[kube-state-metrics] add Controller Selection

[wustus]

What this PR does / why we need it

This PR aims to implement the possibility of deploying the image as a DaemonSet. Currently only Deployment and StatefulSet are supported.
When scraping metrics exported by kube-state-metrics, they will be labeled to originate from the node the pod is running on. In our case some grafana-agent collects metrics exposed by pods and adds an x_host label according to the node this pod is running on. By adding the possibility of running kube-state-metrics as a DaemonSet, metrics are correctly labeled with their node-origin.

Which issue this PR fixes

Implements #4770

Special notes for your reviewer

• I tried to stay backward compatible by adding {{- if eq (.Values.controller | default "deployment") "deployment" }} in a few places.
• daemonset.yaml is a copy of deployment.yaml with removal of .Values.autosharding.enabled and additional setting of the node name env variable according to this.
• When testing, I limited the resources to --resource=pods as is described in the example in the kube-state-metrics repository

Checklist

• DCO signed
• Chart Version bumped
• Title of the PR starts with chart name (e.g. [prometheus-couchdb-exporter])

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[wustus]

This PR addresses a missing feature explicitly described in the kube-state-metrics README. Unless an alternative implementation exists, this should not be considered stale.