User story:

So that I don't complete the wizard with an unsupported version of OS while trying to create a Hypershift control plane cluster, as a user, I want versions that aren't hypershift supported as disabled options in the version drop down

Acceptance criteria:

• Versions that are not hypershift supported are disabled in the version drop-down
• Versions that are hypershift supported are shown and enabled (assuming they pass existing validation rules)
• The version list for a hosted (aka standard ROSA) control plane is not impacted by this change.

Mockups:

-------------------------------------------------------------------------------------------------------------------------------

Implementation details

On the

 https://api.openshift.com/api/clusters_mgmt/v1/versions/

Call there is now a "hosted_control_plane_enable" flag for each version. For example:

{
    "kind": "VersionList",
    "page": 1,
    "size": 234,
    "total": 234,
    "items": [
        {
            "kind": "Version",
            "id": "openshift-v4.12.0",
            "href": "/api/clusters_mgmt/v1/versions/openshift-v4.12.0",
            "raw_id": "4.12.0",
            "enabled": true,
            "default": false,
            "channel_group": "stable",
            "available_upgrades": [
                "4.12.1",
                "4.12.8"
            ],
            "rosa_enabled": true,
            "hosted_control_plane_enabled": false,
            "end_of_life_timestamp": "2024-03-17T00:00:00Z",
 ...

This works should also include unit tests for the version drop down that takes selected ARNs, max version, and hypershift-enabled status into account.