Catalog and schema override settings

[tmasternak]

In some scenarios, clients might want to configure catalog and schema values that are different than the values provided in the connection string or default values on the SQL connection provided by the factory. One of such scenarios is sqlt and sqlp deployment where business, persistence, and transport data are stored in different catalogs and clients want to use native SQL transactions (see this issue].

This will likely require adding fully qualified entity names in the queries executed by the persistence.