test_v3_token_id correctly hash token
test_v3_token_id correctly hash token

The test_v3_token_id test was calculating the token hash by
parsing the response JSON and generating a new JSON document.
This isn't guaranteed to work because a Python dict can have its
fields in any order[1], so the new JSON document may not match the
response JSON and you'd get a different hash. The correct way to
generate a token hash is to use the response as is.

[1] http://docs.python.org/2/library/stdtypes.html#dict.items

Change-Id: I1a79c252916c4459fdc75a6e022d72c0c14582ef

MaheshIBM/keystone,dstanek/keystone,jumpstarter-io/keystone,MaheshIBM/keystone,vivekdhayaal/keystone,vivekdhayaal/keystone,blueboxgroup/keystone,openstack/keystone,mahak/keystone,ging/keystone,reeshupatel/demo,rodrigods/keystone,promptworks/keystone,dstanek/keystone,rajalokan/keystone,openstack/keystone,jamielennox/keystone,nuxeh/keystone,rajalokan/keystone,jumpstarter-io/keystone,takeshineshiro/keystone,ilay09/keystone,klmitch/keystone,rodrigods/keystone,jumpstarter-io/keystone,rushiagr/keystone,takeshineshiro/keystone,reeshupatel/demo,maestro-hybrid-cloud/keystone,rushiagr/keystone,UTSA-ICS/keystone-kerberos,ajayaa/keystone,jonnary/keystone,nuxeh/keystone,roopali8/keystone,idjaw/keystone,promptworks/keystone,dstanek/keystone,rajalokan/keystone,openstack/keystone,blueboxgroup/keystone,nuxeh/keystone,ilay09/keystone,rushiagr/keystone,jamielennox/keystone,cernops/keystone,klmitch/keystone,UTSA-ICS/keystone-kerberos,ging/keystone,maestro-hybrid-cloud/keystone,himanshu-setia/keystone,ilay09/keystone,himanshu-setia/keystone,dims/keystone,mahak/keystone,vivekdhayaal/keystone,ajayaa/keystone,jonnary/keystone,promptworks/keystone,reeshupatel/demo,mahak/keystone,idjaw/keystone,dims/keystone,roopali8/keystone,cernops/keystone