rename instance_info_cache instance_uuid unique constraints

[Dan Prince]

In Folsom we renamed the instance_id column to instance_uuid (see Folsom migration 105 for details). This all went well except that the name of the unique constraints still reflects the old column name.

For MySQL:

instance_id should be named instance_uuid

For PostgreSQL:

instance_info_caches_instance_id_key should be named instance_info_caches_instance_uuid_key

Renaming this unique constraint will allow us to more closely match the automatic naming scheme used by python-migrate and should make naming a bit more consistent.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/16456
Committed: http://github.com/openstack/nova/commit/6d65637dec129863ac4a96bb28b476f032bbff84
Submitter: Jenkins
Branch: master

commit 6d65637dec129863ac4a96bb28b476f032bbff84
Author: Dan Prince <email address hidden>
Date: Mon Nov 19 14:42:54 2012 -0500

    Rename instance_info_cache unique key constraints.

    Rename (via drop and recreate) the instance_uuid unique
    constraints on the instance_info_cache table so they reflect
    the column change name (UUID conversion) we complete in Folsom.

    Fixes LP Bug #1080837.

    Change-Id: I9dd01ebc896c1d7b51c212980e48db16bad18dec