[9.0](backport #7725) chore: update OTel components to v0.122.0

[mergify]

What does this PR do?

Updates the OTel components to v1.28.0/v0.122.0.

This update was performed using following command:

.ci/scripts/otel-update.sh v0.122.0 v1.28.0 v0.122.0 

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

How to test this PR locally

go build .
sudo ./elastic-agent otel

---

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

[mergify]

Cherry-pick of fb3a575 has failed:

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

You are currently cherry-picking commit fb3a5755f.
  (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)

Changes to be committed:
	modified:   NOTICE.txt
	new file:   changelog/fragments/1744022264-update-otel-components-to-v0.122.0.yaml
	modified:   internal/pkg/otel/configtranslate/otelconfig.go
	modified:   internal/pkg/otel/configtranslate/otelconfig_test.go
	modified:   testing/integration/otel_test.go

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

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)

[swiatekm]

I don't think we want to update otel dependencies in patch releases. @mauri870

[mergify]

This pull request has not been merged yet. Could you please review and merge it @mauri870? 🙏

[mauri870]

I don't think we want to update otel dependencies in patch releases. @mauri870

I was not aware of this. Looks like the previous updates were backported #7718, #6774.

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[swiatekm]

I don't think we want to update otel dependencies in patch releases. @mauri870

I was not aware of this. Looks like the previous updates were backported #7718, #6774.

The second one probably shouldn't have been. The first one went in before the final build candidate, which is fine. This is my understanding of our current policy, correct me if I'm wrong @cmacknz.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 63a5faf

History

• 💔 Build #20532 failed e414b92

cc @mauri870

[mauri870]

@swiatekm Thanks for bringing this up today! Given the rationale about breaking changes, I agree that we shouldn't backport this to 9.0, as the breaking changes from elasticsearchexporter mapping::mode could break configuration that was previously working fine, which is not something a user would expect from a patch release.