[9.0] (backport #7936) Use upstream prometheus receiver again

[mergify]

What does this PR do?

Switches from our fork of the Otel prometheus receiver to the upstream version. This fork was driven by a dependency conflict with the prometheus library, which was resolved in elastic/beats#43540.

To achieve this, we bump the beats dependency version. I was also forced to downgrade github.com/elastic/cloud-on-k8s, as it depended on a version of github.com/prometheus/common which was incompatible with the new prometheus library. @pkoutsovasilis I hope that's ok.

Why is it important?

We want to use upstream components where possible.

Checklist

• I have read and understood the pull request guidelines of this project.
  - [ ] 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

---

This is an automatic backport of pull request #7936 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 0c78a0f has failed:

On branch mergify/bp/9.0/pr-7936
Your branch is up to date with 'origin/9.0'.

You are currently cherry-picking commit 0c78a0fb2.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum
	both modified:   internal/pkg/otel/README.md
	both modified:   internal/pkg/otel/configtranslate/otelconfig_test.go

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 5d8f7fd

History

• 💔 Build #20462 failed a7f72e3
• 💔 Build #20461 failed 60cd8c1
• 💔 Build #20414 failed feae808

cc @swiatekm