Add Settings.interpreterSearchPath

[lukaseder]

#8616 introduced Settings.parseSearchPath to allow for specifying a search path to the parser when looking up objects. A similar search path is needed in the DDL interpreter, where we can predict in what schema a table will be located when we interpret CREATE TABLE t (i int) without schema qualification.

Other usages may be thinkable as well.

This feature is required when implementing validation in #9506 (org.jooq.Migration), where we want to make sure no excess objects are located in a target schema. We might not even know that target schema, otherwise.