Remove support for component-prometheus based monitoring

class/defaults.yml

@@ -9,10 +9,6 @@ parameters:
     defaultSourceNamespace: openshift-marketplace
     useCustomNamespace: false
 
-    monitoring:
-      enabled: true
-      instance: null
-
   openshift_operators:
     defaultSource: certified-operators
 

component/main.jsonnet

@@ -30,4 +30,4 @@ local namespace = operatorlib.validateInstance(params.namespace);
       },
     },
   ],
-} + (import 'monitoring.libsonnet')
+}

docs/modules/ROOT/pages/references/parameters.adoc

@@ -71,31 +71,3 @@ default:: `false`
 
 Whether to allow non-standard namespace names for the OperatorGroup.
 If this parameter is set to `true`, the component will allow using namespace names other than `openshift-operators` and `openshift-operators-redhat`.
-
-== `monitoring`
-
-This parameter allows users to enable the component's monitoring configuration.
-Currently the component has support for deploying custom `ServiceMonitors` on clusters which use component `prometheus` to manage a custom monitoring stack.
-
-[WARNING]
-The monitoring configuration is instance independent. It must not be changed between instances of this component.
-
-=== `enabled`
-
-[horizontal]
-type:: boolean
-default:: `true`
-
-Whether to deploy monitoring configurations.
-If this parameter is set to `true`, the component will check whether component `prometheus` is present on the cluster.
-If the component is missing, no configurations will be deployed regardless of the value of this parameter.
-
-=== `instance`
-
-[horizontal]
-type:: string
-default:: `null`
-
-This parameter can be used to indicate which custom Prometheus instance should pick up the configurations managed by the component.
-
-If the parameter is set to the empty string, the default instance configured for component `prometheus` will be used.