Create release workflow

[clairep94]

Issue:

• Stops deploy-staging from triggering on unsuccessful unit test runs & only occur on successful ones
• Update deploy to run after a Github release occurs (currently happens on merges to the release branch)
• Adds release-reminder.yml which runs Tuesday 15:30 UTC -- generates Issue with the create-release workflow link
• Adds release.yml which does two jobs: verify (CI testing) & release (creates the release draft, version, tags, etc). release waits on maintainer approval. If verify fails, the workflow run fails.

Demo:

Changes:

I have verified that this pull request:

• has no linting errors (npm run lint)
• has no test errors (npm run test)
• has no typecheck errors (npm run typecheck)
• is from a uniquely-named feature branch and is up to date with the develop branch.
• is descriptively named and links to an issue number, i.e. Fixes #123
• meets the standards outlined in the accessibility guidelines

[clairep94]

cc: @doradocodes @raclim

[doradocodes]

Wondering if we should really delete after merging, in case we need the branch again later? @raclim what do you think?

[clairep94]

Do you think we should push the branch to retain a history of these?

If so, would it be useful to update this to "release-${{ inputs.newversion }}-auto" (or similar suffix) to track when we're merging releases from the workflow vs. manual?

[doradocodes]

So if the tests fail, will the version get bumped twice?

[clairep94]

No the release.yaml > verify job doesn't include steps for bumping, those are in the release.yaml > release job
The input for version is just captured and used later on the release.yaml > release job (if release.yaml > verify passes)

[doradocodes]

Thanks for working on this so quickly @clairep94 !