Enhance COO to allow troubleshooting panel UI Plugin with custom confuration

[jianrongzhang89]

Currently, when Korrel8r is deployed via the COO UIPugin, COO creates a default configmap with data below:
`
data:
korrel8r.yaml: |
# Default configuration for deploying Korrel8r as a service in an OpenShift cluster.
# Store service URLs assume that stores are installed in their default locations.
stores:
- domain: k8s
- domain: alert
metrics: https://thanos-querier.openshift-monitoring.svc:9091
alertmanager: https://alertmanager-main.openshift-monitoring.svc:9094
certificateAuthority: ./run/secrets/kubernetes.io/serviceaccount/service-ca.crt
- domain: log
lokiStack: https://logging-loki-gateway-http.observability-hub.svc:8080
certificateAuthority: ./run/secrets/kubernetes.io/serviceaccount/service-ca.crt
- domain: metric
metric: https://thanos-querier.openshift-monitoring.svc:9091
certificateAuthority: ./run/secrets/kubernetes.io/serviceaccount/service-ca.crt
- domain: netflow
lokiStack: https://loki-gateway-http.netobserv.svc:8080
certificateAuthority: ./run/secrets/kubernetes.io/serviceaccount/service-ca.crt
- domain: trace
tempoStack: https://tempo-platform-gateway.openshift-tracing.svc.cluster.local:8080/api/traces/v1/platform/tempo/api/search
certificateAuthority: ./run/secrets/kubernetes.io/serviceaccount/service-ca.crt

include:
  - /etc/korrel8r/rules/all.yaml

`

COO reconciles this configmap so that users can not modify it to point to URLs that are different from default ones.

This prevents COO and troubleshoot panel to get deployed in PRODUCTION platforms where customers may be required to deploy those services in different namespaces.