Description

I've split the release workflow into two distinct parts:

1. Create Tag and Release
2. Release Image

This change was made to address an issue in the previous workflow where images were being released with incorrect semantic versioning. By separating the workflows, we now:

• First, create the release tag.
• Then, manually rebuild the nightly image to ensure it includes the correct semver version.
• Finally, trigger the Release Image workflow, which now reliably publishes images with the correct version.

GitHub Issues

List the GitHub issues impacted by this PR:

Checklist:

• Have you run format,vet & lint checks against your submission?
• Have you made sure that the code compiles?
• Did you run the unit & integration tests successfully?
• Have you maintained at least 90% code coverage?
• Have you commented your code, particularly in hard-to-understand areas
• Have you done corresponding changes to the documentation
• Did you run tests in a real Kubernetes cluster?
• Backward compatibility is not broken

How Has This Been Tested?

This is tested in forked repo, created the tag and release, pushed the images to test quay folder