Description of problem:

Installed a ROSA Hypershift cluster with version 4.12.21 in candidate channel. 
Reference command 

rosa create cluster --cluster-name jayacan10hcp --subnet-ids subnet-0a8f9f0b28180cb31,subnet-04dd03178acc5e766 --sts --mode auto --machine-cidr 10.0.0.0/16 --compute-machine-t
ype m5.xlarge --hosted-cp --oidc-config-id 22rif2kh7jagoe7u2ak1caoi74hjrjvj --role-arn arn:aws:iam::301721915996:role/accjayarol-Installer-Role --support-role-arn arn:aws:iam::301721915996:role/accjayarol-Suppo
rt-Role --controlplane-iam-role arn:aws:iam::301721915996:role/accjayarol-ControlPlane-Role --worker-iam-role arn:aws:iam::301721915996:role/accjayarol-Worker-Role --region us-west-2 --version 4.12.21 --channel
-group candidate -y 

Initiated an update to 4.13 latest (i.e. 4.13.4). Cluster has upgraded successfully to 4.13 latest.
But following issues are seen after control plane upgrade.

1. Settings tab indicated a wrong update path from 4.13 to 4.14 and 4.14 is not supported yet for hypershift side and it shouldn't be showing in the update path for hypershift.
2. The cluster upgrade path itself wrong and as result of this the machine pool upgrade itself is not recommended from UI.
   {}{}

Steps to reproduce:

1. Launch OCM UI staging
2. Open ROSA Hypershift cluster ( with a candidate version installed with 4.12.21 version).
3. Go to settings tab, initiate an cluster update to latest 4.13 version.
4. After successful cluster upgrade , verify the control plane upgrade path in settings tab.
5. Verify the machine pool upgrade indication in UI.

Actual results:

1. Settings tab indicated a wrong update path from 4.13 to 4.14 .
2. The cluster upgrade path itself wrong and as result of this the machine pool upgrade itself is not recommended from UI.

Expected results:

1. Settings tab shouldn't be showing any update path from 4.13 to 4.14 as 4.14 is not supported yet for hypershift side.
2. The machine pool upgrade indication should show in UI as the ROSA HCP already in latest available version.