Update OTel components to v0.120.x

[mauri870]

What does this PR do?

Updates OTel components to v0.120.0 (core) and v0.120.1 (contrib).

This is a copy of #6912 with the conflicts fixed.

Why is it important?

We should be keeping the components up to date with upstream as much as possible.

OpenTelemetry Collector Contrib updated its github.com/prometheus/prometheus dependency from v0.54.1 to v0.300.1 in v0.120.0 (open-telemetry/opentelemetry-collector-contrib#36873). This resulted in a conflict with Prometheus v0.54.x dependency in Beats. This forced us to temporarily fork the Contrib, revert the v0.300.x update there (elastic/opentelemetry-collector-contrib#3) and import the forked prometheusreceiver module (ca402c6). This resolves the dependency conflict. This was already done on 9.0 branch in #7411 and now we're doing the same thing on main branch.

The plan is to return to upstream, non-forked components as soon as Beats are updated to Prometheus v0.300.x.

Checklist

• My code follows the style guidelines of this project
• [ ] I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• [ ] I have made corresponding change to the default configuration files
• [ ] I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• [ ] I have added an integration test or an E2E test

How to test this PR locally

go build .
sudo ./elastic-agent otel

[cmacknz]

This is actually pinned at v0.120.0 because v0.120.1 is a bug fix in the prometheus updates that we removed.

Pinning the rest to v0.120.1 is fine as long as we don't pull in both the v0.120.0 and v0.120.1 versions of contrib through this replace.

[mauri870]

/test

[mauri870]

/test

[khushijain21]

/test

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: a674e2c

Failed CI Steps

• x86_64:sudo: default
• x86_64:sudo: default
• x86_64:sudo: fleet-endpoint-security
• x86_64:sudo: fleet-endpoint-security
• arm:sudo: default
• arm:sudo: default
• x86_64:sudo: default
• x86_64:sudo: default
• x86_64:sudo: fleet-privileged
• x86_64:sudo: install-uninstall
• Aggregate test reports

History

• 💔 Build #19476 failed def9cba
• 💔 Build #19443 failed def9cba
• 💔 Build #19438 failed def9cba

cc @mauri870

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b otel-v0.120.0 upstream/otel-v0.120.0
git merge upstream/main
git push upstream otel-v0.120.0

[mauri870]

Closing this since we migrated directly to v0.121.0 in #7686.