X_TENANT_ID or X_ROLE in keystone auth are not deprecated

[Akihiro Motoki]

In neutron/auth.py, X_TENANT_ID and X_ROLE are used to extract context information.
They are now deprecated and X_PROJECT_ID and X_ROLES are recommended instead.
https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/53985
Committed: http://github.com/openstack/neutron/commit/83a3e77e63851c290e2f849db6db555cffb1ef41
Submitter: Jenkins
Branch: master

commit 83a3e77e63851c290e2f849db6db555cffb1ef41
Author: Akihiro MOTOKI <email address hidden>
Date: Sat Oct 26 15:22:45 2013 +0900

    Remove deprecated fields in keystone auth middleware

    This commit makes the following changes:

    Use X_PROJECT_ID instead of X_TENANT_ID:
      In the latest keystone auth_token middleware it is recommended to
      use X_PROJECT_ID instead of X_TENANT_ID. X_PROJECT_ID is supported
      in auth_token middleware for both keystone v2 and v3 API.
      The corresponding change was done in keystoneclient before Grizzly
      release, so we don't need to take care of X_TENANT_ID now.

    USE X_ROLES instead of X_ROLE:
      X_ROLES is now recommended.
      X_ROLE exists just for diablo backward compatibility.

    Remove X_TENANT and X_USER:
      X_TENANT and X_USER are for diablo backward compatibility.
      We no longer need take care of them in Icehouse Neutron.

    Change-Id: Ie714b1323ff8c44dbee66b54e683226cf675b104
    Closes-Bug: #1242447