[Bug] Windows MemoryError on CI runs

[mikealfare]

Is this a new bug in dbt-core?

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

Current Behavior

We've reached the limit for the free tier for Windows CI runs. Adding tests to the current suite causes the Windows py38 run to consistently fail for tests/functional at around 96%. This was verified on a local Windows machine; executing these tests exceeds 8GB of RAM, which is the size of the relevant Windows image.

Long term we should do one of two things:

• Increase the size of the machine, and/or
• Figure out why we're using 8GB of RAM for these tests

Short term, we can unblock ourselves by breaking the test suite into smaller suites in tox.

Expected Behavior

We can run all of the integration tests in one call and get a coverage report that reflects the full suite (you can't add coverage reports together).

Steps To Reproduce

1. Add a sufficient number of integration tests to tests/functional. I added 14 with test data of no more than 2 records.
2. Push to a new branch off of main
3. Run Test and Code Checks against that branch
4. Observe the integration / python 3.8 / windows-latest job

Relevant log output

No response

Environment

- OS: windows-latest
- Python: 3.8
- dbt: `main` (~=1.6.0)

Which database adapter are you using with dbt?

postgres

Additional Context

No response