Use fixed sha image for dependency proxy test

What does this MR do and why?

Stabilizes the dependency proxy test (with Group SAML enabled) by pulling the same image sha which is certain to contain only 1 layer/blob.

Failure: #344484 (comment 743224572)

changed milestone to %14.6

added Quality devopspackage grouppackage registry labels

assigned to @svistas

mentioned in issue #344484 (closed)

added QA label

	1 Message
	CHANGELOG missing: If you want to create a changelog entry for GitLab FOSS, add the Changelog trailer to the commit message you want to add to the changelog. If you want to create a changelog entry for GitLab EE, also add the EE: true trailer to your commit message. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
QA	Will Meek (@willmeek) (UTC+0, same timezone as @svistas)	Sanad Liaquat (@sliaquat) (UTC+5, 5 hours ahead of @svistas)

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

The package-and-qa job from pipeline https://gitlab.com/gitlab-org/gitlab/-/pipelines/416367508 triggered https://gitlab.com/gitlab-org/build/omnibus-gitlab-mirror/-/pipelines/416381010 downstream.

The qa-test job from pipeline https://gitlab.com/gitlab-org/build/omnibus-gitlab-mirror/-/pipelines/416381010 triggered https://gitlab.com/gitlab-org/gitlab-qa-mirror/-/pipelines/416422156 downstream.

The gitlab-qa downstream pipeline failed! .

Unrelated failure

The package-and-qa job from pipeline https://gitlab.com/gitlab-org/gitlab/-/pipelines/416582590 triggered https://gitlab.com/gitlab-org/build/omnibus-gitlab-mirror/-/pipelines/416590502 downstream.

The qa-test job from pipeline https://gitlab.com/gitlab-org/build/omnibus-gitlab-mirror/-/pipelines/416590502 triggered https://gitlab.com/gitlab-org/gitlab-qa-mirror/-/pipelines/416607259 downstream.

The gitlab-qa downstream pipeline failed! .

Allure report

allure-report-publisher generated test report for 43f6d316!

review-qa-smoke: test report
review-qa-all: test report
package-and-qa: test report

approved this merge request

@svistas Looks good to me, thanks!

requested review from @rymai

added typemaintenance label

@rymai, thanks for approving this merge request.

This is the first time the merge request is approved. To ensure full test coverage, a new pipeline has been started.

For more info, please refer to the following links:

• rspec minimal jobs
• jest minimal jobs
• merging a merge request.

enabled an automatic merge when the pipeline for 2a3bf8da succeeds

merged

mentioned in commit 88343240

mentioned in issue gitlab-org/quality/pipeline-triage#109 (closed)

added workflowstaging-canary label

added workflowstaging label and removed workflowstaging-canary label

added workflowcanary label and removed workflowstaging label

mentioned in issue gitlab-org/quality/pipeline-triage#110 (closed)

added workflowproduction label and removed workflowcanary label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label

mentioned in issue gitlab-org/quality/pipeline-triage#135 (closed)

mentioned in issue gitlab-org/quality/pipeline-triage#170 (closed)

mentioned in issue gitlab-org/quality/pipeline-triage#176 (closed)

mentioned in issue gitlab-org/quality/pipeline-triage#179 (closed)