Skip multi-version upgrade job for stable branch MRs

Nailia Iskhakovarequested to merge
tp-skip-multi-version-for-stable-branches into master

What does this MR do and why?

Making multi-version upgrade job for stable branch MRs a manual job where engineer can specify PG dump url and trigger the job if needed.

The job is using latest_upgrade_stop.gz from the latest upgrade stop so on stable branches it wouldn't correspond with the upgrade stop from the version. Refer to Handle GitLab upgrade stop versions in backport... (gitlab-org/quality/quality-engineering/team-tasks#3028 - closed) for more context

See https://docs.gitlab.com/ee/development/database/dbmigrate_multi_version_upgrade_job.html for more context on the job.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

How to set up and validate locally

Not applicable, CI change. Validated with https://gitlab.com/gitlab-org/gitlab/-/pipelines/1461004068 against 17.0 stable branch

Edited by Nailia Iskhakova

Merge request reports