[8.17](backport #7057) [flakiness] kubernetes_secrets provider unit tests

[mergify]

What does this PR do?

This PR introduces the following fixes and improvements:

• Loosens Time Constraints in Unit Tests (needed for certain type of CI runners):

  • The TTLDelete value in test configurations was increased from 2s to 10s, ensuring tests have more leeway in processing cache expiration.
  • The waitForSignal value was adjusted from 1s to 2s to reduce test flakiness.

• Adds Debug Logging for Fetch When Cache is Disabled: relevant comment

  • When the cache is disabled, fetching secrets from the API now logs the retrieved secret’s resource version for better visibility into API interactions.

• Fixes a Typo in a Unit Test Name: relevant comment

  • The test case "key in secret not found" was incorrectly named and is now corrected to "key in secret found".

Why is it important?

Fixes a test failure (Test_Run/secret_no-update_and_no-signal) that caused CI flakiness

Checklist

• I have read and understood the pull request guidelines of this project.
• 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 changes 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

No expected impact on users. These changes are limited to debugging logs and test improvements.

How to test this PR locally

mage test:unit

Related issues

• Relates [Flaky Test]: Test_Run/secret_no-update_and_no-signal – Not equal: expected: "secret_value" actual : "" #6926

---

This is an automatic backport of pull request #7057 done by [Mergify](https://mergify.com).

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 569f455

Failed CI Steps

• arm:sudo: fleet
• arm:sudo: fleet

History

cc @pkoutsovasilis

[elasticmachine]

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