Description of problem:

When PaC releases a new version it becomes the `next` build in the image even if the release is for a lower semver than the current `next` build. For example, PaC v0.36.0 was tagged in June and was included in the nightly build. However in July the nightly build was  updated to reference the most recent release PaC v0.35.3....

The downstream Operator still claims to use PaC v0.36.0 in the Operator description and Konflux users experienced an apparent regression as a result.

Workaround

Override the PaC image in the Subscription environment variables

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

 # Unclear how to reproduce - not sure how this happened yet

Actual results:

Expected results:

Reproducibility (Always/Intermittent/Only Once):

Acceptance criteria: 

The {next} tag should not include the latest release but the release version.

The operator description should correctly reflect the component versions included in the tag.

Definition of Done:

Build Details:

Additional info (Such as Logs, Screenshots, etc):

 *