[Release Improvements] Refresh workflows for the pyproject.toml migration

[mikealfare]

Short description

Migrate dbt-redshift to reference new actions in dbt-labs/actions.

Context

The move to pyproject.toml requires a migration in GHA. Actions are being created in dbt-labs/actions to support this migration; they need to be implemented for dbt-redshift.

Objectives

• Reduce GHA footprint in dbt-redshift
• Standardize dbt-redshift with the same GHA functionality as other adapters
• Minimize dependencies between workflows

PRs

Beta Give feedback

1. [Migrate actions] Create daily-dev-releases workflow
2. [Migrate actions] Create feature-branch-tests workflow
3. [Migrate actions] Create issue-bot workflow
4. [Migrate actions] Create pull-request-bot workflow
5. [Migrate actions] Create pull-request-checks workflow
6. [Migrate actions] Update release workflow
7. [Migrate actions] Create weekly-maintenance workflow

Testing

• New workflows are tested against their dev branch prior to merging

Security

This should not increase security risk, and potentially could reduce it. Any security risks should be addressed as part of dbt-labs/actions#173.

Docs

Each workflow should contain a docstring at the top in the "what/why/when" format.
Some draft work lives in these PRs:

• Workflow formatting updates #780
• Setup hatch #779