Use replicaset and Job MetaGen based on watchers

[ChrsMark]

Respective PR for elastic/elastic-agent-autodiscover#44 part of elastic/elastic-agent-autodiscover#31.

Blocked until elastic/elastic-agent-autodiscover#44 is merged and a new version of the autodiscovery library is released.

How to test this PR

1. Build Metricbeat using DEV=true PLATFORMS=linux/amd64 PACKAGES=docker mage -v package
2. Build a custom docker image out of the previous build using the file from build/package/metricbeat-oss/metricbeat-oss-linux-amd64.docker/docker-build directory.
3. Load the image into a kind cluster using kind load docker-image custom-mb
4. Deploy Metricbeat on k8s using the custom image
5. Verify that k8s module works as expected and also adds the job/cronjob and deployment/replicaset metadata properly.
6. Verify the same as above for the autodiscovery part (hints + templates)
7. Verify the same for the add_kubernetes_metadata processor.

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @ChrsMark? 🙏.
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]

💚 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: 2023-05-30T11:55:46.591+0000

• Duration: 65 min 20 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 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!)

[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 rs_watchers upstream/rs_watchers
git merge upstream/main
git push upstream rs_watchers

[ChrsMark]

@gizas it seems that I don't have permissions to merge this one? Have we changed anything?

BTW both failures are unrelated to this PR's changes.

EDIT: e2e testing suite was using k8s manifests that were missing the required Roles to watch for Jobs. That's the reason for the failing tests. Fixed at elastic/e2e-testing#3530.

[ChrsMark]

@elastic/elastic-agent-data-plane could you approve/merge this one please?

[gizas]

/test

[gizas]

/package

[gizas]

/package

[rdner]

LGTM
The linter issues seem to be false-positives.

[ChrsMark]

e2e tests passed. Merging this one.