Clusterlabel support for Kubernetes alerts

[hoangphuocbk]

Currently, when a Kubernetes alert is fired, for example KubePodCrashLooping, Clusterlabel is not mentioned in description
https://github.com/kubernetes-monitoring/kubernetes-mixin/blob/master/alerts/apps_alerts.libsonnet#L22

            annotations: {
              description: 'Pod {{ $labels.namespace }}/{{ $labels.pod }} ({{ $labels.container }}) is in waiting state (reason: "CrashLoopBackOff").',
              summary: 'Pod is crash looping.',
            },
            'for': '15m',
            alert: 'KubePodCrashLooping',

IMO, we should add clusterLabel to know which Kubernetes cluster the alert is belonged to.

 description: 'Pod {{ $labels.clusterLabel }}/{{ $labels.namespace }}/{{ $labels.pod }} ({{ $labels.container }}) is in waiting state (reason: "CrashLoopBackOff").'

[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 2 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!

[skl]

Fixed by #1011