SignalResponder store access/secret in resource data

We need to stop relying on the logic in heat_keystoneclient which
assumes there is only one keypair per user, as this assumption
may not remain true in future.

So instead, store the access/secret key in the DB as resource data,
which is probably better from a performance perspective anyway, and
will also allow SignalResponder subclasses to potentially override
the default credentials implementation more easily.

Change-Id: I7952181f30c94848acf358ab34cf17b6281d43ac
Partial-Bug: #1089261
blueprint: instance-users
Remove unnecessary setUp call

A setUp method that just upcalls to the parent setUp is redundant and
can be removed.

Change-Id: Id3acee286e551622f4fcfa29934d18e52f4fd47d
Let users specify metadatas on swift accounts.

Change-Id: Ifc9d046759be1be88ad0d7a51dc73ba370a49d8f
Implements: blueprint swift-tempurl
Change loglevel for certain failures

Change Log.info to Log.error/Log.warning to make trouble shooting
more apparent

Change-Id: Ie293df0c941414da8fb035e4d4b170a0a4c9d397
Imported Translations from Transifex

Change-Id: Iff22a95603f04855b25f465df07784f07d17a6ec
Updated from global requirements

Change-Id: I6ddaccfc07132a9d18f3ffdfe1b5919e85b88300
Merge "SignalResponder store access/secret in resource data"
Merge "Imported Translations from Transifex"
Merge "Remove unnecessary setUp call"
Merge "Updated from global requirements"
Merge "Change loglevel for certain failures"
Merge "Let users specify metadatas on swift accounts."