[8.15](backport #5420) [Flaky Test] TestComponentBuildHashInDiagnostics improve agent state check

[mergify]

What does this PR do?

Improves the agent status check on TestComponentBuildHashInDiagnostics to ensure the agent is healthy and has components.

Why is it important?

The test is flaky because the test did not account for the absence of components

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/fragments using the changelog tool
• [ ] I have added an integration test or an E2E test

Disruptive User Impact

• N/A

How to test this PR locally

• run the test with TEST_RUN_UNTIL_FAILURE until you're satisfied or it fails again

Related issues

• Closes Avoid reporting empty version_info for components that just started #5333

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 #5420 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 116e73f has failed:

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

You are currently cherry-picking commit 116e73f952.
  (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)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   testing/integration/package_version_test.go

no changes added to commit (use "git add" and/or "git commit -a")

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

[mergify]

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

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube