Split current Operator API schema into "Pelorus Core" and "Pelorus Exporter"

[mpryc]

We should consider splitting our Pelorus API schema into two parts (we may choose of course different names):

• "Pelorus Core"
  This is to cover all options (except [exporters]) from the: Pelorus Core documentation
• "Pelorus Exporter":
  This is to cover all options from [exporters]

Having this will allow us to add/remove exporters easily without redeploying all other parts such as Prometheus/Grafana easily. Also this could be a benefit when using custom exporters in the future.

[mpryc]

Issues which are somehow related to this topic, with the pelorus operator some of them are not closed, because implementation will change:

• pelorus-operator should have configuration options exposed via custom resources and UI #733
• Helm values in the openAPIV3Schema #751
• add a helm chart option to prevent the deployment of the obsevability stack #451
• Should pelorus cut out the Prometheus/Grafana operators? #369
• Make Pelorus Work with OpenShift User Workload Monitoring #364