We currently reference versions of the CodeQL Action (v1, v2) using branches and not tags. This is nice because it is more consistent with the intention of tags in Git. However it is problematic in terms of Dependabot: users on the v1 or v2 branches won't get Dependabot update PRs, as these are only generated for users on a specific tag or commit SHA.

This PR prepares us to specify releases of the CodeQL Action using tags instead of branches, which will mean our customers who have configured Dependabot for the Actions ecosystem configured will receive a Dependabot update from v1 to v2.

Commit-by-commit review recommended. I'd particularly appreciate a check that I haven't forgot to update any places that use the release branches (i.e. previously v1 and v2, now releases/v1 and releases/v2).

Deployment plan

• Open a PR updating references to v1 and v2 to releases/v1 and releases/v2 respectively. This PR will also automatically update the v1 and v2 tags as part of future release processes. (This is that PR.)
• Wait for this PR to be approved, but don't merge it
• Create branch protection rules for releases/v1 and releases/v2
• Create the v1 and v2 tags manually
• Rename the v1 and v2 branches to releases/v1 and releases/v2 respectively
• Merge the PR (we do this after renaming the branches so we don't trigger any workflows)

Example Dependabot update on a private repo backlinked for maintainers.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Confirm the readme has been updated if necessary.
• Confirm the changelog has been updated if necessary.