Use dynamic schema names rather than hardcoded ones

[dbeatty10]

Describe the feature

To allow all schemas to be PR-specific, replace any hardcoded schema names with the dynamic target.schema that comes from the dbt connection profile.

Additional context

In our CI tests, we have steps like this:

dbt --warn-error run-operation create_source_table

Within that macro, we create a schema named codegen_integration_tests__data_source_schema (which is a hard-coded name):

dbt-codegen/integration_tests/macros/operations/create_source_table.sql

Lines 3 to 6 in fdc998c

	{% set target_schema=api.Relation.create(
	database=target.database,
	schema="codegen_integration_tests__data_source_schema"
	) %}

This could lead to permissions errors if different database users are trying to modify this schema.

Who will this benefit?

This will benefit maintainers that want CI tests to be reliable and robust rather than finicky.

In particular, I think it will help overcome permissions errors faced in these PRs:

• Add support for bigquery testing in GitHub CI via tox #203
• Add support for redshift testing in GitHub CI via tox #204

Are you interested in contributing this feature?