This aims to solve the problem that when we do a build for a release, it comes from the git tag push event. If some containers failed building (which is unfortunately common), we need to re-trigger their builds. Currently, this is only possible by deleting and re-pushing the same tag which has downsides:
1. It starts all Konflux container builds again and so the probability for a failure is not decreased. We just roll the same number of dices in the hope we get all to show 6.
2. Some other release jobs may not be idempotent or in some other way not expect the release git tag be pushed multiple times.

As opposed to repushing tags, it should be possible to recognize when a rebuild is triggered by a /retest comment on GitHub commit and issue image tags with the literal values of git tags.
The limitation is that this would still work only if the last commit on the branch is git-tagged with the expected tag.

See https://redhat-internal.slack.com/archives/C05TS9N0S7L/p1744116339517869

This is a workaround for the time when SRVKP-7442 is not available.

See docs https://pipelinesascode.com/docs/guide/gitops_commands/#event-type-annotation-and-dynamic-variables