Description of problem (please be detailed as possible and provide log
snippests):
ODF-MCO-console is always expecting the managed cluster should have at least ODF-Operator version of 4.11.0. 
Required behavior is:
  ODF Operator version >= ODF Multicluster Orchestrator Operator version.


Version of all relevant components (if applicable):
4.12

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
4.12 ODF-MCO console is strictly dependent on 4.12 ODF-Operator, especially to remove the OCP hybrid console feature gate dependency.

Is there any workaround available to the best of your knowledge?
upgrade ODF-operator version to 4.12

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
100%

Can this issue reproduce from the UI?
100%

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Deploy OCP 4.12 on the Hub cluster.
2. Install ACM 2.6 on the Hub cluster.
3. Install ODF-MCO-Operator on the Hub cluster.
4. Deploy OCP 4.11 on the managed clusters(minimum 2 required).
5. Install ODF Operator 4.11 on the managed clusters.
6. Import all managed clusters into ACM.
7. In UI Go to "All Clusters" view -> Data services -> Data policies.
8. Click Create DRPolicy option.
9. Select the managed clusters.
10. Ui will display error message "spoke-cluster has either an unsupported ODF version or the ODF operator is missing, install or update to ODF 4.11.0 or latest version to enable DR protection."

Actual results:
ODF multicluster console is always suggesting the user keep at least 4.11.0 odf-operator is required.

Expected results:
ODF multicluster console should suggest the minimum required odf-operator version should be greater than or equal to odf-multicluster-orchestrator operator version.

Additional info: