schema override for multi tenant support

[bakoliasn]

Describe your changes

If the override environment variable is set, replaces the table prefix with override and prepends the original prefix to the table name.

How has this been tested?

integration_tests

Reviewer focus

Most changes are in the models and seeds, setting the schema and alias

Checklist before requesting a review

• I have added at least one Github label to this PR (bug, enhancement, breaking change,...)
• My code follows style guidelines
• (New models) YAML files are categorized by sub folder and models listed in alphabetical order
• (New models) I have added a config to each new model to enable it for claims and/or clinical data
• (New models) I have added the variable tuva_last_run to the final output
• (Optional) I have recorded a Loom to explain this PR

Package release checklist

• I have updated dbt docs
• I have updated the version number in the dbt_project.yml

[davidshimamoto]

@bakoliasn Did you mean to fork this and commit this to your fork?

[bakoliasn]

@bakoliasn Did you mean to fork this and commit this to your fork?

Thanks for the heads up! Yes, the goal is to upstream this change so we don’t have to maintain a separate fork. Happy to adjust anything needed to align with your contribution guidelines — just let me know what you'd prefer.

[davidshimamoto]

The process should be:

1. Start a discussion on our community slack around the problem you're trying to solve.
2. Open an issue describing the problem. If it is something extensive, discuss with the team managing the open source.
3. Do the work.

That being said, this is a rather extensive change with architecture choices that requires some thought. I'd like to start by asking if you can elaborate on the problem you're trying to solve here.