Update OTel dependencies to 0.139.0/v1.45.0 and Elastic ones to v0.20.0/v0.21.0

[belimawr]

Commit message

sed -i 's/\(go\.opentelemetry\.io\/collector.*\) v1\.43\.0/\1 v1.45.0/' go.mod
sed -i 's/\(go\.opentelemetry\.io\/collector.*\) v0\.137.0/\1 v0.139.0/' go.mod
sed -i 's/\(github\.com\/open-telemetry\/opentelemetry\-collector\-contrib\/.*\) v0\.137\.0/\1 v0.139.0/' go.mod
go get -u github.com/elastic/opentelemetry-collector-components/...

What does this PR do?

See title

Why is it important?

It updates OTel dependencies

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

Disruptive User Impact

There is a breaking change in the Elasticsearchexporter, batcher is not supported any more, users need to setup a sending_queue now. See open-telemetry/opentelemetry-collector-contrib#42767 for more details.

## How to test this PR locally

Related issues

• Part of Bump EDOT Collector to consume the latest Collector Core (0.138.0 and 0.20.0) #10895
• Beats PR: Update OTel dependencies to 0.139.0/v1.45.0 and Elastic ones to v0.20.0/v0.21.0 beats#47468

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[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 update-otel upstream/update-otel
git merge upstream/main
git push upstream update-otel

[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 update-otel upstream/update-otel
git merge upstream/main
git push upstream update-otel

[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 update-otel upstream/update-otel
git merge upstream/main
git push upstream update-otel

[belimawr]

The failing tests are unrelated to the PR: #5437

[elasticmachine]

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

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 47f34fe

Failed CI Steps

• Win2025:sudo:default
• x86_64:sudo: standalone-upgrade
• x86_64:sudo: default - platform-ingest-elastic-agent-debian-11-1762801856
• x86_64:sudo: fleet-privileged - platform-ingest-elastic-agent-debian-13-1762801856

History

• 💛 Build #30585 was flaky 2367d1a
• 💔 Build #30563 failed c38d9ee
• 💔 Build #30542 failed 70aa772
• 💔 Build #30444 failed 37d1b7d
• 💔 Build #30431 failed c540a2c
• 💔 Build #30376 failed bb453b3

cc @belimawr

[github-actions]

@Mergifyio backport 9.1 9.2

[mergify]

backport 9.1 9.2

✅ Backports have been created

• #11310 [9.1] (backport #11025) Update OTel dependencies to 0.139.0/v1.45.0 and Elastic ones to v0.20.0/v0.21.0 has been created for branch 9.1 but encountered conflicts
• #11311 [9.2] (backport #11025) Update OTel dependencies to 0.139.0/v1.45.0 and Elastic ones to v0.20.0/v0.21.0 has been created for branch 9.2 but encountered conflicts