[8.15](backport #41100) Only watch metadata for ReplicaSets in K8s

[mergify]

Proposed commit message

Use metadata watchers for ReplicaSets in components that need them. The only data we need from ReplicaSets are their name and OwnerReferences, which are used to connect Pods to Deployments and DaemonSets.

This PR makes the change in:

• autodiscovery
• the add_kubernetes_metadata processor

For more details see elastic/elastic-agent#5623.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• 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

You need a full K8s cluster, unfortunately. I've tested it using the default elastic-agent standalone manifest, by building a custom container image and loading it into a local kind cluster.

Related issues

• Relates Agent and beats store too much ReplicaSet data in K8s elastic-agent#5623

---

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

[mergify]

Cherry-pick of ee780d2 has failed:

On branch mergify/bp/8.15/pr-41100
Your branch is up to date with 'origin/8.15'.

You are currently cherry-picking commit ee780d2528.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   CHANGELOG.next.asciidoc
	modified:   libbeat/autodiscover/providers/kubernetes/pod_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum
	both modified:   libbeat/autodiscover/providers/kubernetes/pod.go
	both modified:   libbeat/processors/add_kubernetes_metadata/kubernetes.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally