Add a fixture for Keystone version discovery

As we push out the session and expect people to test with proper URL
responses we should provide a means to create a correct Keystone version
list to test with.

Change-Id: I8309ab6cbc47ad159f3c6e018b60ff8c15c6d917
Modify oauth calls to expect urlencoded responses

Previously, the server side would send jsonwrapped urlencoded
responses. Now we are removing the jsonwrapped portion so that
the responses for oauth calls are just urlencoded.

Related-Bug: #1336910
Change-Id: I0431a581a5c3fca38e22751ef9bde034f0a89a30
Merge "Modify oauth calls to expect urlencoded responses"
Add profiling support to keystoneclient

To be able to create profiling traces for Keystone, client should be
able to send special HTTP header that contains trace info.
This patch is as well important to be able to make cross project
traces. (Typical case nova calls keystone via python client, if
profiler is initialized in nova, keystone client will add extra
header, that will be parsed by special osprofiler middleware in keystone
api)

Don't worry no security issue here, trace information is signed by HMAC
key that is setted in api-paste.ini. So only person that knows HMAC key
is able to send proper header.

Change-Id: Ide6fe268613bb0cc9d9ec6fae2957cc570e9f851
Merge "Add profiling support to keystoneclient"