[prometheus] The future of prometheus(-operator)

[PrivatePuffin]

Is your feature request related to a problem?

Currently we leech some code for prometheus (operator) from upstream.
This should stop, as we dont want any other dependencies besides common.

It also creates huge charts with lots of disables that might or might-not be stable.

Describe the solution you'd like

• We should create our own Prometheus Operator chart (as its a rather simple chart)
• We should move creating Prometheus CRs to common (as we want CR handling in common as a standard)
• We should start maintaining the dashboards ourselves or, preferably, write tooling to fetch them from upstream (which kube-prometheus-stack is also doing)

Describe alternatives you've considered

Keeping things as is.

Additional context

• Its important to note that we dont right-away also have to implement CRs we're not using/supporting actively yet.
• A lot of the CRs are technically speaking, forms of special workload types, it might be nicest to implementing them as such.

I've read and agree with the following

• I've checked all open and closed issues and my request is not there.
• I've checked all open and closed pull requests and my request is not there.