Observability Configuration Phase 1: Create ServiceMonitors for components in the kuadrant operator

[david-martin]

Related RFC Kuadrant/architecture#97

Candidate resources

• https://github.com/Kuadrant/kuadrant-operator/blob/main/config/observability/prometheus/monitors/operators.yaml
• Istio https://github.com/Kuadrant/kuadrant-operator/blob/main/config/observability/prometheus/monitors/istio/service-monitor-istiod.yaml
• EG https://github.com/Kuadrant/kuadrant-operator/tree/main/config/observability/prometheus/monitors/envoy

Simplifies the installation of kuadrant by removing the manual creation of ServiceMonitors, while also allowing users to disable the feature if they’d prefer to create them themselves.

Adding the capability to the sub-operators (authorino, dns, limitador) is out of scope at this time. The goal is to get the feature in front of users more quickly than the time it would take and risk of prioritising implementation in the individual sub-operators and bubbling that up to the kaudrant operator.

The Kuadrant CR configuration will look like this:

observability:
     enable: true

As part of this work, update the guide at https://docs.kuadrant.io/dev/kuadrant-operator/doc/user-guides/full-walkthrough/secure-protect-connect/#optional, and any other locations where Service/PodMonitors are mentioned to reference using this new configuration.
A new guide specifically for enabling Observability, explaining what it does and its intended use would be good to write.