US158341 - Use new release token

[svanherk]

The brightspace-bot and D2L_GITHUB_TOKEN are no longer needed for release workflows. Instead, we have a new D2L_RELEASE_TOKEN that has the ability to bypass the repo ruleset (configured in https://github.com/Brightspace/repo-settings/pull/1466) and org-level ruleset.

Note: This isn't available in the Brightspace org yet, but will be soon!

Before merging, I will:

• Confirm the new ruleset matches the old branch protection rule before deleting it
• Remove brightspace-bot as a repo contributor
• Confirm the D2L_RELEASE_TOKEN is available and remove this repo's access to D2L_GITHUB_TOKEN

If you need to make a cert or hotfix, this will need to be backported to the 20.23.12 and 20.23.11 release branches.

[svanherk]

Looking to get this in before I'm off. Reach out if you have questions/concerns!