Adding kueue-viz templates in helm charts

[akram]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Adds kueue-viz helm charts allowing installation of kueue-viz using helm

Which issue(s) this PR fixes:

Fixes #3853

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Adds kueue-viz helm charts allowing installation of kueue-viz using helm

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue ready!

Name	Link
🔨 Latest commit	15be32a
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/677e48f424e77a00081f32b8
😎 Deploy Preview	https://deploy-preview-3852--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 site configuration.

[mimowo]

@akram please try to make the initial PR minimal, we will add the needed parameters and functionalities in follow ups.

[mbobrovskyi]

/hold for #3849

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: akram
Once this PR has been reviewed and has the lgtm label, please assign tenzen-y 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

[mimowo]

/hold for #3849

/hold cancel
As the PR is merged and the images are already published in https://us-central1-docker.pkg.dev/k8s-staging-images/kueue

[mimowo]

@akram please try to make the initial PR minimal, we will add the needed parameters and functionalities in follow ups.

That was more of a directional comment as it was getting large-ish as a draft, but I'm ok in the current form.

Another thing is that we tend to first provide the config yamls, and then derive the helm charts based on them, so we could follow the pattern here too. PTAL at the visibility configs or prometheus, which are then part of the installable opt-in release artifacts: https://github.com/kubernetes-sigs/kueue/releases/tag/v0.10.0.

While making them release artifacts would be probably the next step I would like to follow the same pattern.