Bump kube-scheduler binary to v1.30 from v1.28 in the user-scheduler

[consideRatio]

We are using a binary of the official kube-scheduler that is now getting too outdated, we should bump it to the latest v1.30. up from v1.28..

We could bump to v1.31, but I think we should try to aim having kube-scheduler at the second newest k8s version because officially kube-scheduler should only be used with a +-1 version to the k8s api-server.

Doing so requires some checks as mentioned by comments next to where kube-scheduler's version is declared.

https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/29f0adb03741ece8fa2b784bb60e85fa3bfa6b0b/jupyterhub/values.yaml#L512-L548

[consideRatio]

Findings from the changelog related to kube-scheduler under API changes

v1.29 changelog

• 'kube-scheduler component config (KubeSchedulerConfiguration) kubescheduler.config.k8s.io/v1beta3 is removed in v1.29. Migrated kube-scheduler configuration files to kubescheduler.config.k8s.io/v1.' (https://github.com/kubernetes/kubernetes/pull/119994, @SataQiu)
• The kube-scheduler selectorSpread plugin has been removed, please use the podTopologySpread plugin instead. (https://github.com/kubernetes/kubernetes/pull/117720, @kerthcet)

v1.30 changelog

Nothing.

v1.31 changelog

Deprecations

Kube-scheduler deprecated all non-csi volumelimit plugins and removed those from defaults plugins.

AzureDiskLimits CinderLimits EBSLimits GCEPDLimits The NodeVolumeLimits plugin can handle the same functionality as the above plugins since the above volume types are migrated to CSI. Please remove those plugins and replace them with the NodeVolumeLimits plugin if you explicitly use those plugins in the scheduler config. Those plugins will be removed in the release 1.32. (https://github.com/kubernetes/kubernetes/pull/124500, @carlory) [SIG Scheduling and Storage]

API changes

• Fixed incorrect "v1 Binding is deprecated in v1.6+" warning in kube-scheduler log. (https://github.com/kubernetes/kubernetes/pull/125540, @pohly) [SIG API Machinery]