otel: skip flaky test TestMetricbeatOTelMultipleReceiversE2E

[mauri870]

Proposed commit message

This test is flaking with a high failure rate. I suspect it has to do with running multiple receivers on the same process, since the single receiver version of this test (TestMetricbeatOTelReceiverE2E) is not flaking.

This test was introduced by #45427.

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.

Disruptive User Impact

How to test this PR locally

$ cd x-pack/metricbeat/
$ go test -c -tags otelbeat
$ mage docker:composeUp
$ go test -tags "integration" -run 'TestMetricbeatOTelMultipleReceiversE2E' ./tests/integration -v -count=1

=== RUN   TestMetricbeatOTelMultipleReceiversE2E
    otel_test.go:297: Flaky test, see https://github.com/elastic/beats/issues/45631
--- SKIP: TestMetricbeatOTelMultipleReceiversE2E (0.00s)
PASS
ok      github.com/elastic/beats/v7/x-pack/metricbeat/tests/integration 0.005s

Related issues

• For [Flaky Test] x-pack/metricbeat/tests/integration TestMetricbeatOTelMultipleReceiversE2E and TestFilebeatOTelMultipleReceiversE2E #45631.

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

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

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @mauri870? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[mauri870]

Skipping backports since this test only exists in main.

[mauri870]

/test