Release the operator v0.120.0

[codeboten]

As per open-telemetry/opentelemetry-collector#12411

[iblancasa]

@yuriolisa you are the next in the release doc.

[thiagogcm]

collector-contrib 0.120.0 shipped with the new prometheus client (open-telemetry/opentelemetry-collector-contrib#36873)

shouldn't this release match that version as well?
my point is mainly because of the prometheus config in the target allocator (https://github.com/open-telemetry/opentelemetry-operator/blob/main/cmd/otel-allocator/internal/config/config.go)

as the prometheus receiver supports the new scrape configs, one might think the target allocator also does

[swiatekm]

collector-contrib 0.120.0 shipped with the new prometheus client (open-telemetry/opentelemetry-collector-contrib#36873)

shouldn't this release match that version as well? my point is mainly because of the prometheus config in the target allocator (https://github.com/open-telemetry/opentelemetry-operator/blob/main/cmd/otel-allocator/internal/config/config.go)

as the prometheus receiver supports the new scrape configs, one might think the target allocator also does

I don't think this is required. The operator defines its level of support for Prometheus features by publishing the prometheus-operator version we're compatible with, and the Prometheus dependency follows from that relationship. We do want to upgrade to the latest versions of these dependencies sooner rather than later, but this shouldn't block the operator release. Especially given that the upgrade is not trivial, and we don't want to break things inadvertently.