Add custom Metrics tags for ClusterQueue

[ecdatadog]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Following the issue #7066, this PR proposes an implementation to inject some labels in kueue metrics (in this PR, it only shows the clusterQueue one but can be expected to other components such as localQueue) from k8s label/annotations.

It relies on :

 metrics:
   bindAddress: :8080
   enableClusterQueueResources: true
   customMetricTags:
      clusterQueue:
        - resourceTag: team
        - resourceTag: user
        - resourceTag: gpu_type
          overrideMetricTag: my_gpu_type

There are different know issues of this PR :

• not properly managing the metrics doc
• not handling the validation that the prometheus tag is a valid one for prometheus. (by default , the recent prometheus client accepts any UTF-8 but the legacy label name validator was more strict)

Which issue(s) this PR fixes:

Fixes #7066

Special notes for your reviewer:

It is a draft PR that is only to discuss about what could be the implementation for #7066

Does this PR introduce a user-facing change?

NONE

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue ready!

Name	Link
🔨 Latest commit	2c3f194
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-kueue/deploys/6932fdf2f971e40008afce48
😎 Deploy Preview	https://deploy-preview-8099--kubernetes-sigs-kueue.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[linux-foundation-easycla]

• ❌ - login: @ecdatadog / name: Etienne Carriere . The commit (2c3f194) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ecdatadog
Once this PR has been reviewed and has the lgtm label, please assign mimowo for approval. For more information see the 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

[k8s-ci-robot]

Welcome @ecdatadog!

It looks like this is your first PR to kubernetes-sigs/kueue 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kueue has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @ecdatadog. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.