Story
EaaS cluster to always use the same OpenShift (OCP) version as the one configured in the release test pipeline for a given release, so that release validation is performed against the correct and intended OCP version.

Background
Currently, the OCP version used by the EaaS cluster is not explicitly tied to the OCP version defined in the release test pipeline for a specific release branch. This can lead to a mismatch between the environment where release tests are validated and the actual target OCP version intended for that release.
For example, if the release test pipeline for the 1.20 next branch is executed against OCP 4.18, the EaaS cluster used for that execution should also run on OCP 4.18 to ensure accurate and consistent test results.

Goal
Introduce a dependency such that the EaaS cluster automatically aligns with and uses the same OCP version defined in the corresponding release test pipeline.

Approach

• Add an explicit OCP version dependency configuration in the release test pipeline.

• Ensure the EaaS cluster provisioning logic dynamically consumes this OCP version value from the pipeline configuration.

• Validate that the correct OCP version is selected and applied before test execution begins.

• Add safeguards to prevent pipeline execution if the specified OCP version cannot be provisioned in EaaS.

Acceptance Criteria

1. When a release test pipeline is configured to run on a specific OCP version (e.g., OCP 4.18), the EaaS cluster used for that execution must be provisioned with the same OCP version.

1. The OCP version used by EaaS must be derived automatically from the release test pipeline configuration, with no manual intervention required.

1. If the specified OCP version is unavailable in EaaS, the pipeline must fail early with a clear and actionable error message.

1. No regression should be introduced to existing release pipelines that already execute successfully.