DefaultRecordBinding.pgRenderRecordCast and others don't apply schema mapping

[lukaseder]

There are quite a few jOOQ internals that use a Named::getQualifiedName and render that directly, without giving schema mapping any consideration. One example is DefaultRecordBinding.pgRenderRecordCast, which might not apply schema mapping.

We should have an ExecuteListener in our integration tests that looks for references of the default schema in ordinary generated SQL (e.g. public), and then tries applying a schema mapping public -> xyz, to check if all public references have been replaced correctly by xyz). With that ExecuteListener added to every integration test, we'll have much higher test coverage of the schema mapping feature.

The above test has exposed the following missing schema mappings (at least):

• UDT casts in PostgreSQL (e.g. CAST(? AS PUBLIC.MY_TYPE), though enum types are cast correctly)
• CREATE FUNCTION and DROP FUNCTION (e.g. PostgreSQL)
• CREATE PROCEDURE and DROP PROCEDURE
• CREATE TRIGGER and DROP TRIGGER (this has been recognised as a TODO of Add support for { CREATE | DROP } TRIGGER commands #6956, in a code comment)
• CREATE INDEX (e.g. H2)
• Stored function calls with no schema in SQL Server (which still require a schema, see Error when rendering SQL Server procedures with Settings.renderSchema == false #2569)

[lukaseder]

I'll treat this as an umbrella issue to fix all sorts of missing schema mapping applications, see updated issue description

[lukaseder]

The UDT stuff has changed a bit in jOOQ 3.17, which is why I won't backport the fix to 3.16 and older minor releases...

[lukaseder]

Fixed in jOOQ 3.18.0 and 3.17.2 (#13765)