This change allows swift TempURLs to be used to signal heat from
server deployments.
When signal_transport: TEMP_URL_SIGNAL is specified, the following will happen:
* On creation a swift object will be created with an associated TempURL for PUTs
* The PUT URL is used for the deploy_signal_id input value, along with the new
deploy_signal_verb input being set to PUT
* In the deployment resource check_complete, the swift object is polled for
new signal contents, and signal() is called when the swift object contents change
By specifying deployment signal_transport: TEMP_URL_SIGNAL and
server software_config_transport: POLL_TEMP_URL it should now be possible to use
config/deployment resources with only a keystone v2 API (or with a standalone heat)
Implements-Blueprint: software-config-swift-signal
Change-Id: I1dfba248dcfc90c3d872ba35f0aa935cca5c5606
7470a5e919