Take the schema into account when looking up Pg unique constraints.

This fixes the "ERROR: An object of class
UR::DataSource::RDBMS::UniqueConstraintColumn already exists...' error
due to us having multiple tables (in different schemata) with the same
name and primary key.

Change-Id: I67816888ecee58dc11ee942d2ee4fcde6064ea87