"Deliver Container Image" doesn't reflect the custom-tag

[tumido]

Describe the bug
Sometimes I have to use the "Deliver Container Image" issue template to trigger a build pipeline which failed on release, like recently with the PSI issues... The problem is that when I trigger the "Deliver Container Image" build with the newest tag in the repo, the custom-tag is not respected and is kept outdated, while the version tag image is updated properly.

To Reproduce
Steps to reproduce the behavior:

1. set custom-tag in .aicoe.yaml
2. Have a version tag in the repo, let's say v1.0.0
3. Create "Deliver Container Image" issue with the same tag v1.0.0
4. Let it build
5. Watch the image repository. The v1.0.0 image is updated, while the image with the custom-tag is left outdated.

Expected behavior
If triggered on the latest release tag, update the custom-tag image pointer as well.

Additional context
When it happened to me. A this time the v3.2.0 is the latest release and .aicoe.yaml has set custom-tag: latest
aicoe-aiops/sync-pipelines#60

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[harshad16]

/remove-lifecycle stale

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[harshad16]

/lifecycle frozen