chore(helm): remove duplicate keys in resources (backport #4681)

[mergify]

This is an automatic backport of pull request #4681 done by Mergify.
Cherry-pick of 610662a has failed:

On branch mergify/bp/release-1.6/pr-4681
Your branch is up to date with 'origin/release-1.6'.

You are currently cherry-picking commit 610662ae0.
  (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:   app/kumactl/cmd/install/testdata/install-tracing.defaults.golden.yaml
	modified:   app/kumactl/cmd/install/testdata/install-tracing.overrides.golden.yaml
	modified:   app/kumactl/data/install/k8s/tracing/jaeger/all-in-one-template.yaml

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   app/kumactl/cmd/install/testdata/install-control-plane.with-egress.golden.yaml
	both modified:   app/kumactl/cmd/install/testdata/install-control-plane.with-helm-set.yaml
	both modified:   app/kumactl/cmd/install/testdata/install-control-plane.with-ingress.golden.yaml
	deleted by us:   app/kumactl/cmd/install/testdata/install-cp-helm/fix4496.golden.yaml
	deleted by us:   app/kumactl/cmd/install/testdata/install-observability.defaults.golden.yaml
	deleted by us:   app/kumactl/cmd/install/testdata/install-observability.no-grafana.golden.yaml
	deleted by us:   app/kumactl/cmd/install/testdata/install-observability.no-loki.golden.yaml
	deleted by us:   app/kumactl/cmd/install/testdata/install-observability.no-prometheus.golden.yaml
	deleted by us:   app/kumactl/cmd/install/testdata/install-observability.overrides.golden.yaml
	deleted by us:   app/kumactl/data/install/k8s-deprecated/tracing/jaeger/all-in-one-template.yaml
	both modified:   deployments/charts/kuma/templates/egress-deployment.yaml
	both modified:   deployments/charts/kuma/templates/ingress-deployment.yaml

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

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com