[8.19](backport #51684) chore: update OTel Collector dependencies to v0.155.0/v1.61.0

[mergify]

Proposed commit message

Updates the OpenTelemetry Collector dependencies to the current latest versions v0.155.0 and v1.61.0. See changes since v0.154.0/v1.60.0 for Core and Contrib.

Why is it important?

We want to be on the latest version to keep up with latest features and bug fixes.

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.next.asciidoc or CHANGELOG-developer.next.asciidoc.

How to test this PR locally

make mage
(cd auditbeat && mage build)
(cd filebeat && mage build)
(cd metricbeat && mage build)
(cd x-pack/filebeat && mage build)
(cd x-pack/metricbeat && mage build)
```<hr>This is an automatic backport of pull request #51684 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 539bc0e has failed:

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

You are currently cherry-picking commit 539bc0e2b.
  (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:   .buildkite/x-pack/pipeline.xpack.otel.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum
	both modified:   x-pack/otel/distributions/beats-otel-collector/manifest.yaml

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

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
• /test : Run the Buildkite pipeline.

[infra-vault-gh-plugin-prod]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[github-actions]

TL;DR

All 33 failed Buildkite jobs are caused by unresolved cherry-pick conflict markers in the backport PR, not by independent beat/test failures. The check/update jobs fail because go.mod cannot be parsed, and the pre-commit jobs fail on check-merge-conflict.

Remediation

• Resolve the backport conflicts in go.mod, go.sum, NOTICE.txt, and x-pack/otel/distributions/beats-otel-collector/manifest.yaml, keeping the intended OTel Collector v0.155.0 / v1.61.0 dependency updates.
• After committing the resolved files, rerun the failed Buildkite pipeline or at least pre-commit run --all-files plus the affected make -C <beat> check update && make check-no-changes jobs.

Investigation details

Root Cause

This is a configuration / backport conflict failure. Mergify reported that cherry-picking 539bc0e2bfb921ea90dae91506839d6d08826762 into 8.19 left unmerged paths in NOTICE.txt, go.mod, go.sum, and x-pack/otel/distributions/beats-otel-collector/manifest.yaml. The PR diff also contains conflict markers in go.mod, for example around the github.com/prometheus/common and OTel dependency updates.

Because the conflict markers are committed in dependency/config files, every beat-specific check fails before reaching beat-specific tests.

Evidence

• Build: https://buildkite.com/elastic/beats/builds/48794
• Failed job pattern: Run check/update across beats exits while installing mage / parsing go.mod.
• Representative log excerpt from filebeat-filebeat-run-checkupdate.txt:

../go.mod:107: malformed module path "<<<<<<<": invalid char '<'
../go.mod:126: malformed module path "<<<<<<<": invalid char '<'
../go.mod:178: malformed module path "<<<<<<<": invalid char '<'
../go.mod:254: malformed module path "<<<<<<<": invalid char '<'
make: *** [../dev-tools/make/mage-install.mk:10: mage] Error 1

• Representative log excerpt from filebeat-filebeat-run-pre-commit.txt:

check for merge conflicts................................................Failed
- hook id: check-merge-conflict

go.sum:242: Merge conflict string '<<<<<<<' found
x-pack/otel/distributions/beats-otel-collector/manifest.yaml:51: Merge conflict string '<<<<<<<' found
go.mod:107: Merge conflict string '<<<<<<<' found

Verification

Not run locally; the CI failure is deterministic from committed conflict markers and occurs before package tests can execute.

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[mergify]

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

[andrzej-stencel]

@copilot fix the conflicts in go.mod file by keeping the more recent versions of each dependency. Then run go mod tidy && make notice and commit the changes to the branch.

[Copilot]

@copilot fix the conflicts in go.mod file by keeping the more recent versions of each dependency. Then run go mod tidy && make notice and commit the changes to the branch.

Done. Resolved all conflict markers in go.mod and go.sum by keeping the more recent versions of each dependency (e.g. prometheus/common v0.68.1, bbolt v1.5.0, smithy-go v1.26.0, OTel v1.61.0/v0.155.0), then ran go mod tidy and make notice. Committed in 7a7f1ce.

[mergify]

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

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request