Don't run lint, rspec, and other such jobs on dev.gitlab.org after tagging

Summary

During the patch release https://gitlab.com/gitlab-org/release/tasks/-/issues/20236, dev.gitlab.org suffered from severe capacity issues: production#20142 (closed). We had to stop some automatic builds and retry pipelines sequentially, which is time consuming and toil that RMs should not have to repeat during every security release.

One of the findings during the incident was that the tag pipeline for GitLab runs several lint and rspec jobs on the tag. We don't care about the rspec output once the package has been tagged because we test our packages thoroughly before reaching tagging anyway (we only tag a commit if the pipeline is already green for that commit)

Sample tag pipeline on dev.gitlab.org: https://dev.gitlab.org/gitlab/gitlab-ee/-/pipelines/389943

By reducing these jobs, we will reduce the load on dev.gitlab.org when we create multiple tags for multiple codebases.

This was also discussed on Slack:

Acceptance Criteria

• Don't trigger CI jobs in the fixtures, lint, test, and other similar stages in a tag pipeline on dev.gitlab.org for the GitLab-EE and GitLab-CE codebases