use genfeaturegates utility in k/k to update feature gate info

[dims]

Using code being added to kubernetes main repo in:
kubernetes/kubernetes#135510

We need automation to keep the information in k/website fresh. in the above PR we are adding a utility which we can reuse here.

This essentially deprecates the custom gist i have been maintaining for a while:
https://gist.github.com/dims/a0ecf5de51235968e12b9d6b62ac3a83/

Description

Issue

Closes: #

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name	Link
🔨 Latest commit	02e08b9
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-vnext-staging/deploys/692c4216cd6b310008786cba

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

• content/en/docs/OWNERS
• scripts/releng/OWNERS

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

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	02e08b9
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/692c421637270d0008f28909
😎 Deploy Preview	https://deploy-preview-53489--kubernetes-io-main-staging.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.

[kfess]

Thank you for this great tool.

I've noticed that when users want to understand the details of a feature gate,
they often need to manually search for the corresponding KEP in k/enhancements
(I find myself doing this frequently).

What do you think about including KEP search links in the generated output?
The k/k code can already output these links as linkKEPs.

This might be out of scope for this PR, but I wanted to share the idea
for future consideration.

[dims]

@kfess i am putting the framework in place between the 2 repos. I am happy for folks to morph this as they see fit to add more things! (KEP owners, SIGs etc)

[lmktfy]

/hold

Only because some (just a few) of the files that this PR would add aren't yet complete. I want to call that out so we can decide how to handle that.

Approvers for English, for the website overall, @dims, and of course SIG leadership: any of you can unhold this and you definitely wouldn't need to check with me before you do that.

---

One option (there are others!) is to split this PR: the first part can add the tooling, the second part can update all the feature gates where we have a description for them, and a third manually-curated PR could add in the feature gates that are missing.

If we have the appetite for it, we could also backport those changes to the v1.34 docs, or use the same automation against the v1.34 release.

[k8s-ci-robot]

PR needs rebase.

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.

[dims]

I have no issues however you all want to handle this. please feel free to take it over as i won't have time.

thanks,
Dims