Description of problem:
I see that when HighNodeUtilization is enabled on scheduler and lowNodeutiliztion is enabled on descheduler, descheduler does not throw any error on a hypershift cluster.

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

How reproducible:
Always

• Steps to Reproduce:*
  1. Install hypershift cluster
  2. Now use the hosted cluster kubeconfig
  3. Install descheduler with `LowNodeUtilization` startegy enabled
  4. Now use the mgmt cluster
  5. Enabled highNodeUtilization for scheduler by running the command `oc patch hostedcluster <guestClusterName> -n <hostedClusterName> --type=json -p [{"op": "add", "path": "/spec/configuration", "value":{"scheduler": {"profile":"HighNodeUtilization"}

  }}]`
  6. wait for kubescheduler pods in the mgmt cluster to restart
  7. Now run the command `oc logs -f <kube_descheduler_operator_pod`

• Actual results:*
  See that no errors are seen

Expected results:
Errors should be seen in the descheduler operator pod log which reads `"enabling Descheduler LowNodeUtilization with Scheduler HighNodeUtilization may cause an eviction/scheduling hot loop"`

• Additional info:*
  Enabling HighNodeUtilization for scheduler in mgmt cluster has been fixed in 4.14, see https://issues.redhat.com/browse/OCPBUGS-7091 for more details.

hostedClusterName -> can be retreived from command `oc get hc -A` on the mgmt cluster of hypershift