Presubmit to check for tag moves

[puerco]

We keep image tags in the Kubernetes registries immutable. While the image promoter does not support moving them, it is not evident to contributors that promotion manifests should not attempt to change them.

We should create a presubmit to check image promotion manifests to ensure tags are not moved to another digest this would prevent us spending community resources to spin up a promoter job which will ultimately fail.

Here is an example of a job failing due to a tag move: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-k8sio-image-promo/1536425226437398528

/sig release
/sig k8s-infra
/kind feature
/priority important-longterm

Slack ref: https://kubernetes.slack.com/archives/CCK68P2Q2/p1655153080206009

[ameukam]

/help

[k8s-ci-robot]

@ameukam:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[afzal442]

Any suggestion will be great.

cc @ameukam

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ameukam]

/remove-lifecycle stale
/lifecycle frozen