Updating NewPod updater with autodiscover 0.6.7 version

[gizas]

• Enhancement

What does this PR do?

This PR aligns the elastic-agent-autodiscover version of elastic agent with one in beats, the 0.6.7

Why is it important?

It is mandatory because after elastic/beats#37338 we have upgraded to version 0.6.7 the beats repo and still elastic-agent has an older version of elastic-agent-autodiscover.

This Pr makes the configuration needed on kubernetes provider to support 0.6.7 elastic-agent-autodiscover
Related PR in beats elastic/beats#37431

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

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Relates Check Pod Autodiscover conditions for node/namespace updates beats#37338
• Relates Bump github.com/elastic/elastic-agent-autodiscover from 0.6.6 to 0.6.7 #4109

[mergify]

This pull request does not have a backport label. Could you fix it @gizas? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[gizas]

/test

[gizas]

/test

[gizas]

/test

[gizas]

/test

[elastic-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube