[ADAP-1053] [Bug] Tracking common hanging schemas post ci/cd test runs

[McKnight-42]

Is this a new bug in dbt-redshift?

• I believe this is a new bug in dbt-redshift
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

We appear to have a few tests that slowly build up in redshift database post ci/cd and local test runs due to not being properly dropped. the tests in question are related to test_basic, test_incremantal_unique_id, and possibly _sources. at least the first two are for most part defined in dbt-core and simply imported into dbt-redshift so we may need to move up stack to core to check teardown methods defined there and see if schema name changes in redshift are just not being caught.

Expected Behavior

that all schemas created by running our unit/functional tests should be deleted at end of test run as part of teardown, or defined cleanup methods.

Steps To Reproduce

run ci/cd, and then either query or check your test database to see if any artifacts remain.

Relevant log output

No response

Environment

- OS:
- Python:
- dbt-core:
- dbt-redshift:

Additional Context

No response