[8.19] (backport #11025) Update OTel dependencies to 0.139.0/v1.45.0 and Elastic ones to v0.20.0/v0.21.0

[mergify]

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?
• ...

---

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

[mergify]

Cherry-pick of ad43a0d has failed:

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

You are currently cherry-picking commit ad43a0dbd.
  (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:   .gitignore
	modified:   magefile.go
	new file:   pkg/testing/fs.go
	modified:   testing/integration/ess/otel_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE-fips.txt
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum
	both modified:   internal/edot/go.mod
	both modified:   internal/edot/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)

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: c8c9eda

Failed CI Steps

• Start ESS stack for integration tests
• x86_64:sudo: container - platform-ingest-elastic-agent-debian-13-1762801856

History

• 💔 Build #30726 failed 5cb41b0
• 💔 Build #30721 failed f7ac547

cc @belimawr