When modifying the .releaserc file it would be nice to see a dry-run
for what will happen when the branch is override.

Brought up in https://gitlab.com/gitlab-com/gl-infra/data-access/durability/gitlab-backup-cli/-/merge_requests/15#note_2356952141

feat: update all CI templates to pull common-ci-tasks images from $CI_REGISTRY instead of registry.gitlab.com

Including secret configuration source.

Instead of running npm install on each install cycle.

Upgrades semantic release, and adds the `semantic-release-major-tag`
plugin.

Updates the goreleaser task to use Vault.

chore(semantic-release): Print a deprecation warning when `$SEMANTIC_RELEASE_GITLAB_TOKEN` is unset.

Previously, if a user provided the `vault` input, it was ignored if either the
`$SEMANTIC_RELEASE_GITLAB_TOKEN` or `$GITLAB_TOKEN` variable was set. With this
change, we'll always use the token from Vault if explicitly provided by the
user.

Issue: gitlab-com/gl-infra/common-ci-tasks#15

… when deciding between Vault and CI variable.

Issue: gitlab-com/gl-infra/common-ci-tasks#15

The previous check, `$SEMANTIC_RELEASE_GITLAB_TOKEN != ""` appears to be
interpreted as "not defined or not empty" (i.e. the inversion of "defined and
empty"), which returns `true` if the variable is not defined. That is not the
intention here.

Issue: gitlab-com/gl-infra/common-ci-tasks#15

Previously, the `semantic_release` job required its token to be stored in a CI
variable. With this change, the token can optionally be stored in Vault
instead, while keeping the previous behavior as the default.