[oteltest][fbreceiver] Fix flaky test

[VihasMakwana]

In our otelbeat's test cases, we use require.EventuallyWithT to test certain conditions which are satisfied after some time. For eg. status reporter.
While asserting conditions, we should pass *assert.CollectT variable and not the parent testing.T. Passing the parent variable will lead to instant failure because of the underlying logic of EventuallyWithT.

Closes #45057

[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!)

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @VihasMakwana? 🙏.
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.

[elasticmachine]

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

[mauri870]

Can you check the tests that use this suite as well, to make sure they do not use t inside AssertFunc? Thank you!

[VihasMakwana]

Can you check the tests that use this suite as well, to make sure they do not use t inside AssertFunc? Thank you!

yeah, there are some occurrences. I'll update the PR.