Verify deploy keys settings for protected tags (backport)

What does this MR do and why?

Contributes to #384371 (closed)

Verify deploy key permissions for protected tags creation.

The fix process described here: #384371 (comment 1338397839)

Main MR for %15.11 - !116780 (merged)

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch.
• The original MR has been deployed to GitLab.com (not applicable for documentation or spec changes).
• This MR has a severity label assigned (if applicable).
• Ensure the e2e:package-and-test-ee job has either succeeded or been approved by a Software Engineer in Test.

Note to the merge request author and maintainer

The process of backporting bug fixes into stable branches is tracked as part of an internal pilot. If you have questions about this process, please:

• Refer to the internal pilot issue for feedback or questions.
• Refer to the patch release runbook for engineers and maintainers for guidance.

assigned to @vyaklushin

added backend bugfunctional groupsource code labels

added typebug label

added devopscreate sectiondev labels

changed milestone to %15.10

marked the checklist item This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch. as completed

marked the checklist item The original MR has been deployed to GitLab.com (not applicable for documentation or spec changes). as completed

added severity4 label

marked the checklist item This MR has a [severity label] assigned (if applicable). as completed

mentioned in issue #384371 (closed)

added feature flag label

	2 Warnings
	Most of the time, merge requests should target master. Otherwise, please set the relevant Pick into X.Y label.
	The e2e:package-and-test-ee job needs to succeed or have approval from a Software Engineer in Test. Read the "QA e2e:package-and-test-ee" section for more details.

QA e2e:package-and-test-ee

@vyaklushin, the package-and-test job must complete before merging this merge request.*

If there are failures on the package-and-test pipeline, ping your team's associated Software Engineer in Test (SET) to confirm the failures are unrelated to the merge request. If there's no SET assigned, ask for assistance on the #quality Slack channel.

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

Generated by Danger

Allure report

allure-report-publisher generated test report!

e2e-package-and-test: test report for 4bd6914b

expand test summary

+-----------------------------------------------------------------------+
|                            suites summary                             |
+------------------+--------+--------+---------+-------+-------+--------+
|                  | passed | failed | skipped | flaky | total | result |
+------------------+--------+--------+---------+-------+-------+--------+
| Configure        | 0      | 0      | 6       | 0     | 6     | ➖     |
| Plan             | 120    | 0      | 0       | 46    | 120   | ❗     |
| Verify           | 104    | 0      | 18      | 102   | 122   | ❗     |
| Create           | 322    | 0      | 14      | 136   | 336   | ❗     |
| Manage           | 132    | 0      | 6       | 60    | 138   | ❗     |
| Secure           | 14     | 0      | 10      | 14    | 24    | ❗     |
| Analytics        | 4      | 0      | 0       | 4     | 4     | ❗     |
| Package          | 0      | 0      | 6       | 0     | 6     | ➖     |
| Govern           | 88     | 0      | 2       | 88    | 90    | ❗     |
| Fulfillment      | 4      | 0      | 44      | 0     | 48    | ✅     |
| Monitor          | 16     | 0      | 0       | 16    | 16    | ❗     |
| Release          | 12     | 0      | 0       | 10    | 12    | ❗     |
| Framework sanity | 0      | 0      | 2       | 0     | 2     | ➖     |
| Growth           | 0      | 0      | 4       | 0     | 4     | ➖     |
| ModelOps         | 0      | 0      | 2       | 0     | 2     | ➖     |
+------------------+--------+--------+---------+-------+-------+--------+
| Total            | 816    | 0      | 114     | 476   | 930   | ❗     |
+------------------+--------+--------+---------+-------+-------+--------+

marked the checklist item Ensure the e2e:package-and-test-ee job has either succeeded or been approved by a Software Engineer in Test. as completed

Hi @igor.drozdov! It's a backport for %15.10 that you reviewed before: !116780 (merged).

Can you please verify this one as well?

requested review from @igor.drozdov

resolved all threads

approved this merge request

@igor.drozdov, thanks for approving this merge request.

This is the first time the merge request is approved. Please ensure the e2e:package-and-test-ee job has succeeded. If there is a failure, a Software Engineer in Test (SET) needs to confirm the failures are unrelated to the merge request. If there's no SET assigned to this team, ask for assistance on the #quality Slack channel.