fix(check-latest-tag-in-changelog): skip job if tag is an alpha or beta release
When pushing alpha or beta tags to feature or other branches, it is undesirable to run the check-latest-tag-in-changelog check. This proposed rule matches tags for the standard SemVer pre-release format, with or without a leading v and with or without a trailing integer, and skips the job if a match is found. Examples of tags that would match (and skip this job) include:
v1.0.0-beta1.0.0-beta.32.0.0-alpha.1
An example of a current failure that blocked a beta release for testing can be seen here: https://gitlab.developers.cam.ac.uk/uis/devops/infra/terraform/gcp-monitoring/-/pipelines/901814
The same beta release using the proposed template, which skips the changelog check, is shown here: https://gitlab.developers.cam.ac.uk/uis/devops/infra/terraform/gcp-monitoring/-/pipelines/901832