Update API version from kubescheduler.config.k8s.io/v1beta3 to kubescheduler.config.k8s.io/v1

[JoeyC-Dev]

Description

Using stable API kubescheduler.config.k8s.io/v1 instead of beta API kubescheduler.config.k8s.io/v1beta3.

We should not use beta API when it is graduated to stable.

For your convenience: https://github.com/search?q=repo%3Akubernetes%2Fwebsite+path%3Acontent%2Fen%2Fdocs%2F+kubescheduler.config.k8s.io%2Fv1beta3&type=code

The following page is not included:
https://kubernetes.io/docs/concepts/scheduling-eviction/scheduler-perf-tuning/
(Reason: this page is outdated and should be edited via another PR, while this PR only includes some small changes.)

Issue

Closes: #50240

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	ce341fb
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/67e379da689e3c0008342328
😎 Deploy Preview	https://deploy-preview-50241--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 site configuration.

[tengqm]

/lgtm
Not sure if the config file has anything changed.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 86d37ff6a16f2662ffe1445d62ec623d6ac06f99

[JoeyC-Dev]

/lgtm Not sure if the config file has anything changed.

At least from API reference, I don't see anything wrong.

Quick links:
https://kubernetes.io/docs/reference/config-api/kube-scheduler-config.v1/#kubescheduler-config-k8s-io-v1-NodeAffinityArgs
https://kubernetes.io/docs/reference/config-api/kube-scheduler-config.v1/#kubescheduler-config-k8s-io-v1-PodTopologySpreadArgs

/assign salaxander

[kundan2707]

thanks for updating

[kundan2707]

/lgtm

[tengqm]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tengqm

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

The pull request process is described here

Needs approval from an approver in each of these files:

• content/en/docs/OWNERS [tengqm]

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