Use upstream go plugins helpers

[kaanyalti]

• Enhancement

Proposed commit message

Switched from using the archived https://github.com/elastic/go-plugins-helpers to its upstream https://github.com/docker/go-plugins-helpers.

Please explain:

• WHAT: patterns used, algorithms implemented, design architecture, message processing, etc.
• WHY: Elastic's go-plugins-helpers package is archived and is not maintained anymore. Replaced it with the upstream repo which is still maintained.

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.

Author's Checklist

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @kaanyalti? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

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

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[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: 2024-04-18T21:29:26.549+0000

• Duration: 150 min 1 sec

Test stats 🧪

Test	Results
Failed	0
Passed	29390
Skipped	2061
Total	31451

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the 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!)