As an analytics engineer, I want to be able to configure the name of the test database in the drop_branch_schemas macro

[emekdahl-palmetto]

Subject of the issue

The test branch name is hardcoded into the macro. Make it parameterized so that others can configure it for their specific setups.

example: {%- if target.database != "TEST" -%}

Your environment

• Version of palm
• Operating system
• Docker / Docker compose version
• Relevant dependencies and versions

Steps to reproduce

Try testing with a database that isn't named "TEST"

Expected behaviour

Pass name of test database in the macro as a param

Actual behaviour

"TEST" is hardcoded in the macro

[jakeberesford-palmetto]

We probably want to use an env vars for this?