Escape schema/tablenames in metadata.getTables()

[nvoxland]

Description

Escape _'s and %s in schema/table names used in getTables() because so that searches for a table with an _ in them won't also match tables without them, since the jdbc method uses those in LIKE operations

Fixes #1604

---

Dev Handoff Notes (Internal Use)

Links

• Fixed Issue: Underscore in schemaName causes error relation "databasechangelog" already exists #1604
• Test Results: https://github.com/liquibase/liquibase/pull/2398/checks

Testing

• Steps to Reproduce: Underscore in schemaName causes error relation "databasechangelog" already exists #1604
• Guidance:
  • Impact: Changes escaping logic for snapshotting tables in all databases except oracle, mssql, and db2z for tables with "_" or "%" in their names.

Dev Verification

Replicated issue by running changelog:

    <changeSet id="1" author="example">
        <createTable tableName="testTable">
            <column name="id" type="int"/>
        </createTable>
    </changeSet>

with defaultSchemaName=test_schema and then with defaultSchemaName="test-schema" on postgresql. After those two successful updates, any future runs against defaultSchemaName=test_schema failed. NOTE: the reproduction does depend a bit on how the database returns rows back internally. I initially tried testrschema as an alternative to test_schema but it worked because test_schema came back before testrschema in the problem query.

┆Issue is synchronized with this Jira Bug by Unito

[XDelphiGrl]

The setup of the schemas and objects makes for a really nice, readable test validation. I wish I'd thought of this when I was doing the manual tests! :) Thanks for the test, @nvoxland.