prometheus, grafana, jaeger, kiali

_Clarifying this issue to be with product operators (for community, see: https://issues.redhat.com/browse/OSSM-5274).

Unlike 2.x, for 3.0, these addons will NOT be installed all at once. Users will progressively add more things, validating that each addon is working. For users who want a "quick and dirty" setup for PoCs/demos, the community addons can be installed very quickly as will be documented in OSSM-5274.

Rough Addon workflow:

1. Install OSSM operator and create Istio CRD
2. Install Istioctl (to be productized - https://issues.redhat.com/browse/OSSM-5)
3. Install Gateway(s) - https://issues.redhat.com/browse/OSSM-5273 (should be the same - or very similar to project doc)
4. Install Bookinfo and validate that ProductPage is accessible - return to this to generate metrics and traces for next steps.
5. Integrate with OpenShift user workload monitoring (Documented here for OSSM2)]
   1. Aside, we may want to add dashboards for Istio, Istiod metrics..
6. Integrate with Kiali operator and CRD. 
7. Integrate with Distributed Tracing operator(s) and CRD(s). Use tech preview OTEL / Tempo integration if possible. (Jaeger to be deprecated).
8. Validate that 'istioctl dashboard ...' and Kiali dashboard links work to access different dashboards. This may require additional to config.

Notes:

• Put together, the documentation for the above will be roughly equivalent to our OSSM2 onboarding doc. This will largely form the initial OSSM3 product doc. cc rhn-support-tokeefe gmonahan 
• To be complete, the above should use product operators (including an OSSM3 product operator), though the Sail operator can be used until we have an OSSM3 product operator.
• Productizing Istioctl may be non-trivial... can use upstream Istioctl until we have a productized istioctl.