[beatreceiver] fix status reporting

[khushijain21]

Proposed commit message

This PR updates the status of a beatreceiver if it fails to start.

Checklist

• [x] My code follows the style guidelines of this project
• [x] 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
• [x] I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
• [ ] I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

None

Related issues

• Closes https://github.com/elastic/beats/issues/47848

[github-actions[bot]]

:robot: GitHub comments

Just comment with:

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

[mergify[bot]]

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

[pierrehilbert]

@khushijain21 I think we should backport this

[cmacknz]

Is there a test we can add for this?

[pierrehilbert]

FYI, @khushijain21 will be out until the day before the FF so we should probably ask someone to take it over if we want this test to be added.

[cmacknz]

Yes we need this bug fixed as it's definitely affected people, and yes we need a test showing this correctly fixed the bug.

[khushijain21]

I updated the tests and also added output from manual testing