Add support for ScrapeConfig CRD to prometheus.operator

[alex-berger]

PR Description

Adding support for ScrapeConfig, initially only supporting StaticConfig.

Feedback and guidance highly appreciated.

Which issue(s) this PR fixes

Fixes #1428

Notes to the Reviewer

PR Checklist

• CHANGELOG.md updated
• Documentation added
• Tests updated
• Config converters updated

[CLAassistant]

All committers have signed the CLA.

[clayton-cornell]

Doc suggestions are almost all style related to align with incoming style changes for the component docs.

The two important questions that need clarification are:

1. Is this an Experimental, Public preview, or GA component?
2. Is this a Community supported component?

[clayton-cornell]

Will this one be a Community supported component?

[alex-berger]

I am definitively not the authority to answer this questions :-). However, reading https://github.com/grafana/alloy/blob/main/docs/developer/adding-community-components.md my intuition is that it should have the same status as the other prometheus.operator components (servicemonitors, podmonitors and probes).

---

Some additional thoughts/checks regarding https://github.com/grafana/alloy/blob/main/docs/developer/adding-community-components.md:

The community components category is mainly targeted at vendor-specific components for which Grafana does not offer commercial support (for example the Datadog exporter).

It's neither vendor specific nor proprietary, and I assume we can safely say that those Prometheus Operator CRDs are kind of an open (source) de-facto standard.

Avoid overlapping functionalities.

AFAIK, this component closed a feature gap and I am not aware of overlapping functionalities.

Avoid components that can be implemented as modules.

AFAIK, this component closed a feature gap and I am not aware of achieving the same with modules.

Avoid components that affect our dependencies in an undesired way, such as pulling in an incompatible version or bloating the collector.

Should be OK, as it depends on the same dependencies as the other prometheus.operator components.

Make sure that the code licenses are compatible with Alloy's [license](https://github.com/grafana/alloy/blob/main/LICENSE).

Should be OK, as it depends on the same dependencies as the other prometheus.operator components.

Clicked the wrong button in the review screen.