heat standalone mode should work with keystone v3

[Steve Baker]

Heat standalone currently only works with the v2 keystone backend. Possibly all that is required is for auth_password.KeystonePasswordAuthProtocol to (optionally) create a v3 client when creating a token.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/141908

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/141908
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=a17e0ee4c60bdc704621394602e1f0d43707750a
Submitter: Jenkins
Branch: master

commit a17e0ee4c60bdc704621394602e1f0d43707750a
Author: Steve Baker <email address hidden>
Date: Thu Dec 18 10:41:34 2014 +1300

    Use configured auth for standalone middleware

    Previously auth_password.KeystonePasswordAuthProtocol directly created
    a keystone v2 client, which means that heat-standalone wouldn't
    work if heat-engine is using the default KeystoneClientV3 client.

    This change creates a heat_keystoneclient.KeystoneClient and uses that to
    fetch the data required to build the authenticated env to pass to the
    request context. This means that the standalone middleware will now work
    with the default v3 keystone backend, the contrib v2 backend, or any other
    valid implementation of KeystoneClient. The type of KeystoneClient is
    determined by the heat.conf keystone_backend value, which means that this
    value is now read by heat-api when using the standalone middleware.

    For v3 the service catalog is left empty, which means heat-engine will fetch
    it again.

    Change-Id: I46d4edbfffdb0e606e4f4c767610c137d03495f4
    Closes-Bug: #1402472