Description of problem: If the managed hypershift is upgrading failing, it fails to get the clusterVersion, there's an issue with tracking it - https://issues.redhat.com/browse/ACM-12011.

It impacts opersfhitVersion label generated. Observability uses openshiftVersion label to deploy different image on OCP or *KS, so it impacts Obs deployment on this failing upgrade hypershift.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1. import hypershift
2. hypershift reports upgrade failing
3. enable Observability
4. Observability takes this cluster as the *ks and not deploy on this hypershift correctly.

Actual results:

Expected results:

Additional info: