<!--- This environment context section helps us quickly review your PR. 
      Please take a minute to fill-out this information. -->

## Environment
**Liquibase Version**: 4.3.3

**Liquibase Integration & Version**: Spring Boot 2.4.5

**Database Vendor & Version**: PostgresQL 12 w/ Timescale Extension

**Operating System Type & Version**: Linux 5.11

## Description
I am attempting to call an extension function that is added by the Timescale extension via a migration using a \<sql\> element. When the migration runs, I get an error indicating that the function doesn't existing with the given arguments. However, I have confirmed that the function is present by running the exact same SQL against the database directly.

I have used a similar call in the past and had success, so I eventually discovered that this sort of thing used to work in 3.7.0, but no longer works in 4.3.3. It seems like something is now configured in Liquibase such that it can't find these extension functions (schema related perhaps?).

This seems like it might be related to: https://github.com/liquibase/liquibase/issues/1821, but I wasn't sure.

## Steps To Reproduce
1) Run Timescale docker image (timescale/timescaledb:2.0.1-pg12)
2) Attempt to run a migration calling the create_hypertable extension function, or any extension function I suspect ```<sql>select create_hypertable('schema.table', 'timestamp');</sql>```
3) Run migration

## Actual Behavior
Migration fails with:

ERROR: function create_hypertable(unknown, unknown) does not exist
Hint: No function matches the given name and argument types. You might need to add explicit type casts.

## Expected/Desired Behavior
Migration succeeds.


/**
     * Convenience method for when the schemaName is set but we don't want to parse the body
     */
    public static void surroundWithSchemaSets(List<Sql> sql, String schemaName, Database database) {
        if ((StringUtil.trimToNull(schemaName) != null) &&
                !ChangeLogParserConfiguration.USE_PROCEDURE_SCHEMA.getCurrentValue()) {
            String defaultSchema = database.getDefaultSchemaName();
            if (database instanceof OracleDatabase) {
                sql.add(0, new UnparsedSql("ALTER SESSION SET CURRENT_SCHEMA=" + database.escapeObjectName(schemaName, Schema.class)));
                sql.add(new UnparsedSql("ALTER SESSION SET CURRENT_SCHEMA=" + database.escapeObjectName(defaultSchema, Schema.class)));
            }
            else if (database instanceof AbstractDb2Database) {
                sql.add(0, new UnparsedSql("SET CURRENT SCHEMA " + schemaName));
                sql.add(new UnparsedSql("SET CURRENT SCHEMA " + defaultSchema));
            }
        }
    }
    /**
     * Convenience method for other classes similar to this that want to be able to modify the procedure text to add the schema
     */
    public static String addSchemaToText(String procedureText, String schemaName, String keywordBeforeName, Database database) {
        if (schemaName == null) {
            return procedureText;
        }
        if ((StringUtil.trimToNull(schemaName) != null) && ChangeLogParserConfiguration.USE_PROCEDURE_SCHEMA.getCurrentValue()) {
            StringClauses parsedSql = SqlParser.parse(procedureText, true, true);
            StringClauses.ClauseIterator clauseIterator = parsedSql.getClauseIterator();
            Object next = "START";
            while ((next != null) && !next.toString().equalsIgnoreCase(keywordBeforeName) && clauseIterator.hasNext()) {