Make Quick Checks be skipped on release preparation PRs. Add new version check specific to release preparation PRs.

[SarahFrench]

Problem

This PR's changes are intended to allows PRs made during the release process to skip running all the 'Quick Checks'.

These example PRs made during releases show how the changes are limited CHANGELOG.md, .changes/***, and version/VERSION files, so running the full test suite isn't necessary.

• Alpha release : prepare for 1.11.0-alpha20241211 release #36194
• Patch release :
  • prepare for 1.10.2 release #36195
  • Prepare for 1.10.5 release #36384

However the PRs should still run unit tests for the version package. This ensures the new value for version/VERSION is correct, which is important as the value impacts the final built binaries in a release.

After these changes we need to make sure all tests still run against pushes to the main branch/important branches.

Solution

I've made the checks.yml workflow into a reusable workflow, and made workflow files for these different scenarios:

• Running checks in the context of a push to main or release branches
• Running checks when pushing to a non-protected feature branch
• Running checks on PRs

Creating multiple workflows that reuse checks.yml is necessary because we cannot define multiple push triggers in a single workflow. Defining multiple push triggers is required to enable us to distinguish a push to protected versus non-protected branches.

Also, this PR also introduces a new workflow that will run tests to check the version value is correct when a PR contains changes limited to the version package.

Ideas not in this PR

We could introduce the use of concurrency groups to avoid PRs running tests in duplicate (push and pull_request triggers). However I think that'd be useful to introduce separately, to avoid this PR being too complicated.

[SarahFrench]

It looks like there are some settings on this repo that this PR affects. I believe this repo expects Quick Checks to always be present on PRs, so this PR breaks that expectation by renaming the checks and future PRs that skip Quick Checks may have merging blocked also.