[Bug]: KubeQuota alerts can have duplicate series

[skl]

What happened?

Affects the following alerts:

1. KubeQuotaAlmostFull
2. KubeQuotaFullyUsed
3. KubeQuotaExceeded

Found during testing with duplicate KSM installation on GKE:

found duplicate series for the match group

{cluster="duplicate", namespace="gke-managed-system", resource="pods", resourcequota="gcp-critical-pods"}

on the right hand-side of the operation:

[
  {__name__="kube_resourcequota", cluster="duplicate", instance="grafana-k8s-monitoring-kube-state-metrics.monitoring.svc:8080", job="integrations/kubernetes/kube-state-metrics2", namespace="gke-managed-system", resource="pods", resourcequota="gcp-critical-pods", type="hard"},
  {__name__="kube_resourcequota", cluster="duplicate", instance="grafana-k8s-monitoring-kube-state-metrics.monitoring.svc:8080", job="integrations/kubernetes/kube-state-metrics", namespace="gke-managed-system", resource="pods", resourcequota="gcp-critical-pods", type="hard"}
];

many-to-many matching not allowed: matching labels must be unique on one side

Please provide any helpful snippets.

What parts of the codebase are affected?

Alerts

I agree to the following terms:

• I agree to follow this project's Code of Conduct.
• I have filled out all the required information above to the best of my ability.
• I have searched the issues of this repository and believe that this is not a duplicate.
• I have confirmed this bug exists in the default branch of the repository, as of the latest commit at the time of submission.

[github-actions]

This issue has not had any activity in the past 30 days, so the
stale label has been added to it.

• The stale label will be removed if there is new activity
• The issue will be closed in 7 days if there is no new activity
• Add the keepalive label to exempt this issue from the stale check action

Thank you for your contributions!