Release tooling: Initial empty canary release workflow

[JReinhold]

What I did

This PR is the first step of building the canary release workflow. For me to be able to trigger it and try it out, the workflow needs to exist on next. So we now add an no-op workflow, so I can start triggering it and modifying it in another branch.

https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch

How to test

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "build", "documentation", "maintenance", "dependencies", "other"]

[github-actions]

	Fails
🚫	PR is not labeled with one of: ["ci:normal","ci:merged","ci:daily"]

Generated by 🚫 dangerJS against 39c72fa

[ndelangen]