Enable tagging existing image with image-builder

[kolodziejczak]

Description

We @kyma-project/goat, would like to create a following release pipeline:

1. Run tests that do not require image (units etc)
2. Build an image with a working tag like v20241112-13ghags, but without release tag (eg. 1.8.)
3. Run tests that require module image (e2e)
4. If e2e tests are successful - tag the existing image, created in the previous steps with a release tag (eg. 1.8.0)
5. Create release

To do that, we need to be able to tag an existing image with a new, different tag.

Reasons

Create proper release pipeline. Currently in a situation where the e2e tests fails against the release artifact and it cannot be proceed, the artifact already exists with a release tag. In addition teams are not able to delete this artifact on their own.

Enable teams to create clean release pipeline, with the good practices applied. Remove eventual dependency to another team during unsuccessful release.

Acceptance Criteria

• [ ] image-builder allows to tag existing image with another tag in the same workflow run

Attachments

[Ressetkk]

I would also be nice if we could re-tag and sign images in the pipeline environment during the promotion of an artifact.

inputs:

• reference to existing image, eg. local.kyma/dev/image:vDATE-sha
• reference to new image, eg. production.kyma/image:VERSION

outputs:

• processed reference to new image production.kyma/image:VERSION

requirements:

• download image with the remote digest (do not use docker, as it changes the digest of an image in its local registry)
• change image reference
• push image to new path
• sign new image with remote signing service