feat: Add a selector for runtime volume metrics

[shorim]

Description

Changes proposed in this pull request (what was done and why):

• Add a selector in MetricPipeline CRDs for enabling/disabling the collection of volume metrics
• Refactor the creation of metric_groups list in kubeletstats receiver: a metric group is now only added to the list if at least one MetricPipeline has the corresponding input selector enabled. This will let us avoid sending unnecessary metrics to the gateway which will be dropped by all pipelines.
• Extract the checks for the enabled inputs to the metrics pkg, so that it can be used in both gateway and agent packages
• In order to add the k8s.volume.type resource attribute to volume metrics, extra_metadata_labels field is added to the kubeletstats receiver and the permission for the agent to read the nodes/proxy resource is added to the ClusterRole of the agent
• Add filter/drop-non-pvc-volumes-metrics in agent to filter only for PVC volume metrics and drop metrics from other volumes types
• Add filter/drop-runtime-volume-metrics in gateway to drop volume metrics for pipelines in which volume metrics are disabled
• Add unit and e2e tests
• Adjust busola ConfigMap for MetricPipeline

Changes refer to particular issues, PRs or documents:

• Enhance runtime input with selectors for PVC volumes #1301

Traceability

• The PR is linked to a GitHub issue.
• The follow-up issues (if any) are linked in the Related Issues section.
• If the change is user-facing, the documentation has been adjusted.
• If a CRD is changed, the corresponding Busola ConfigMap has been adjusted.
• The feature is unit-tested.
• The feature is e2e-tested.

[kyma-bot]

New changes are detected. LGTM label has been removed.