WIP: feat: Add SELinux metrics

[jsafrane]

What this PR does / why we need it:
This is a proof of concept for metrics suggested by SELinuxMount feature.

Using these metrics I think with lot of joins and label replaces I can detect if two containers use the same volume in parallel, and the containers have the same SELinux label (good) or a different one (bad, those Pods will not run when SELinuxMount gets enabled).

New metrics:

• kube_pod_security_context: pod's spec.securityContext fields. The only values I need are seLinuxOptions.
• kube_pod_container_security_context: pod's spec.containers[*].securityContext fields. I need privileged flag + seLinuxOptions.
• kube_pod_container_volume_mount: report volumes used by containers. The existing kube_pod_spec_volumes_persistentvolumeclaims_info tracks volumes used in pods.
• kube_csidriver_info: report CSIDriver object fields. I need just seLinuxMount flag.

WIP. TODO when the KEP is approved:

• Add RBACs for reading CSIDriver objects.
• Add unit tests + docs.
• Add more labels to the metrics. What other SecurityContext, PodSecrutyContext and CSIDriver fields are useful?
• Add proposed pod spec.securityContext.seLinuxChangePolicy to kube_pod_security_context.
• Consider adding kube_persistentvolume_unique_volume_id. kube_persistentvolume_info does misses some volume types (e.g. in-tree vSphere or Cinder) and is declared STABLE. And it's clumsy to work with.

How does this change affect the cardinality of KSM: increases
(no change to any existing metric, new metrics do have nozero cardinality)

KEP update proposal: kubernetes/enhancements#4843

[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-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jsafrane
Once this PR has been reviewed and has the lgtm label, please assign rexagod for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment