`deployment` label on ReplicaSet (Pod?) metrics

[IncandescentChrysalis]

What would you like to be added:
deployment label on ReplicaSet metrics, potentially Pod.

Why is this needed:
As of today, it is impossible to aggregate Pods based on a Deployment they belong to.

Describe the solution you'd like

Additional context

• https://github.com/kubernetes/kube-state-metrics/blob/v2.12.0/docs/deployment-metrics.md
• https://github.com/kubernetes/kube-state-metrics/blob/v2.12.0/docs/replicaset-metrics.md
• https://github.com/kubernetes/kube-state-metrics/blob/v2.12.0/docs/pod-metrics.md

Potentially related to the feature #2424, which addresses objects relationship through dedicated metrics.
The path taken is different, but would also allow for the current use case.

[k8s-ci-robot]

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[IncandescentChrysalis]

/remove-lifecycle stale