[OSSM-8136] Add Kiali version into kiali cr + improve stability of TestOpenShiftMonitoring test

[mkralik3]

• Added Kiali version to the Kiali CR to not install the same version as the operator version ( since now, it is 1.89 operator version )
• Added waiting for Prometheus target to be ready before requesting the mesh app.

Passed on all SMCP versions: https://master-jenkins-csb-servicemesh.apps.ocp-c1.prod.psi.redhat.com/job/maistra/job/maistra-test-tool/2769/

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[jewertow]

not use standalon kiali CR but patch the existing one (managed by maistra operator) instead. (the way how the customer should use it)

You are not correct saying that customers should not use custom Kiali CR. SMCP intentionally allows to "attach" custom Kiali CR to SMCP. I see 2 reasons to keep custom Kiali as is:

1. We documented this approach.
2. OSSM 3 does not support Kiali out of the box and attaching custom Kiali is the way to integrate with OSSM 3, and users migrating to that version have to follow this approach.

[mkralik3]

@jewertow yeah, you are right, the mention is here https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/service_mesh/index#ossm-smcp-kiali_kiali-config-ref , my bad ( I thought that only istio operator should manage kiali, also that was told me on kiali slack )

I will rewrite the test back to use kiali version explicitly to fix the issue.

[mkralik3]

Updated description and the code