Consider search_path when looking up type OIDs in TypeInfoCache

In case when types with the same name existed in several schemas,
TypeInfoCache did not consider the current search_path and was choosing
an OID of a type not deterministically. These change will make
the type from the current schema to be chosen. Also this change remains
backwards compatible with the previous implementation, still being anble
to find a type, that is not included into the current search_path.

Though the fix changes the behavior of TypeInfoCache, MetaData logic
still does not consider search_path, when reflecting database objects.