Improve debug output for K8s tests

[pkoutsovasilis]

What does this PR do?

Add dumping all logs of the pods in the namespace of the TestKubernetesAgentStandalone test when this fails

Why is it important?

This helps in debugging the reason of this k8s test failing

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

force TestKubernetesAgentStandalone to fail and check that the pod logs are getting saved. You can check the artifacts produced here of such a case

Related issues

• Closes Improve debug output for K8s tests when the pod fails to start #5171

[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

[pkoutsovasilis]

@rdner is this something to what you are after? 🙂

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[rdner]

Thank you!