kiali operator cannot determine kiali version when installing ossmc

[jmazzitelli]

Install Sail, Kiali, OSSMC using all community operators. The operator auto-detects Kiali and installs OSSMC fine and it works. However, it does not log the kialiVersion correctly:

$ oc get ossmconsole ossmconsole -n ossmconsole -o jsonpath='{.status.environment}' | jq
{
  "kialiVersion": "unknown",
  "kubernetesVersion": "1.26.5+7a891f0",
  "openshiftVersion": "4.13.3",
  "operatorVersion": "v1.78.0"
}

Find out why it can't figure out the version and fix that.

[jmazzitelli]

I think the reason for this is that the Kiali CR and the OSSMConsole CR were created at roughly the same time. So the Kiali pod didn't fully start by the time the version check ran. Perhaps we can add a simple while loop here so it can retry a few times before giving up. The version field isn't necessary for OSSMC to function properly, but it is very helpful for debugging and support.

[jmazzitelli]

The additional benefit of this is that the OSSMConsole won't be installed until Kiali endpoint is fully ready. Therefore, as soon as the plugin is running, the user should be able to use it right away (as opposed to waiting for Kiali to be ready or, most likely, getting some odd behavior of the plugin because it can't talk to Kiali initially).