Use external autodiscover library for hints helpers

[ChrsMark]

What does this PR do?

Make use of the external github.com/elastic/elastic-agent-autodiscover/utils library to replace local implementation of hints' helpers.

Hints helpers were move to the external library with elastic/elastic-agent-autodiscover#19 and elastic/elastic-agent-autodiscover#20

Why is it important?

With this transition the external library is the single source of truth and will be used by Beats and Elastic-Agent from now on whenever possible.

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.next.asciidoc or CHANGELOG-developer.next.asciidoc.

How to test this PR locally

Ci checks should be enough

Related issues

• Relates Add hints' utils to autodiscover library elastic-agent-autodiscover#19 Move hints helpers under utils and add tests elastic-agent-autodiscover#20

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b update_autodiscover_lib upstream/update_autodiscover_lib
git merge upstream/main
git push upstream update_autodiscover_lib

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-06-29T11:07:10.830+0000

• Duration: 137 min 17 sec

Test stats 🧪

Test	Results
Failed	0
Passed	22390
Skipped	1937
Total	24327

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

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

[MichaelKatsoulis]

Except those lint errors looks good!

[ChrsMark]

E2E tests' failures seem irrelevant. Merging this one.