if OS console is not enabled, then either skip doing things or fail with a human readable error

[jmazzitelli]

fixes: https://issues.redhat.com/browse/OSSM-2134

[jmazzitelli]

I may need to check the other code that installs ConsoleLinks - that may need to be skipped, too.
UPDATE: This is done. PR now handles ConsoleLinks

[jmazzitelli]

to test, log into an openshift cluster with istio installed, podman login to the internal image registry and:

1. make cluster-push operator-create kiali-create
2. confirm kiali is installed
3. make ossmconsole-create
4. confirm ossmc is installed
5. uninstall ossmc and kiali via make ossmconsole-delete kiali-delete and make sure no errors occurred and everything uninstalled
6. Follow instructions to disable the console: https://docs.openshift.com/container-platform/4.13/web_console/disabling-web-console.html but here's how to easily do it: oc patch consoles.operator.openshift.io cluster -p '{"spec": {"managementState": "Removed" }}' --type=merge ... at this point, the state should be "Removed" which you can confirm via oc get consoles.operator.openshift.io cluster -o jsonpath='{.spec.managementState}{"\n"}'
7. make kiali-create
8. confirm kiali is installed
9. make ossmconsole-create
10. Confirm you do NOT have OSSMC installed and that the operator logs an error message (oc get ossmconsole ossmconsole -n ossmconsole -oyaml). The error expected is found in the status field and should look something like this:

  - ansibleResult:
      changed: 1
      completion: 2023-10-25T18:11:31.568587
      failures: 1
      ok: 11
      skipped: 3
    lastTransitionTime: "2023-10-25T18:11:31Z"
    message: The OpenShift Console is not installed and enabled. Cannot install OSSMC.
    reason: Failed
    status: "False"
    type: Failure

When you are all done, you can put your Console back to normal via:

oc patch consoles.operator.openshift.io cluster -p '{"spec": {"managementState": "Managed" }}' --type=merge

[jshaughn]

Test steps worked as described. One bonus, after re-enablingthe console the existing CR was processed by the operator and the OSSMC was "magically" installed.