Add Redshift internal build process workflow

[VersusFacit]

resolves #38 in epic

Problem

We need a workflow to release things internally

Solution

Write the workflow. I'll be opening up a PR for the workflow this one calls.

Followup actions including reconfiguring secrets and doing a full run start to finish!

Checklist

• I have read the contributing guide and understand what's expected of me
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

[emmyoop]

Looks good - mostly some questions/changes for the inputs.

[emmyoop]

Just noting this needs to be updated once the dbt-release PR gets merged.

Suggested change

	uses: VersusFacit/dbt-release/.github/workflows/internal-archive-release.yml@main
	uses: dbt-labs/dbt-release/.github/workflows/internal-archive-release.yml@main

[emmyoop]

@mikealfare can this be done without ~=?

[mikealfare]

I would need to look at it, but I would think so. We would need to update the function to return a tuple, something along the lines of "dbt-postgres>={},<{}".format(_plugin_version()) where _plugin_version() == (1.8.0b1, 1.9).

[emmyoop]

Approving as is for now with the understanding that more PRs will follow on after testing since none of this can be tested before the workflow gets merged. Since this is a workflow that will be manually submitted there is little risk in this approach.

[mikealfare]

Tests are failing here due to the ddtrace break. This is an unrelated issue. The primary motivation of merging this PR is to get a workflow in main that can be tested in a future PR. This PR represents partial, and on-going work.