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.

zero-to-jupyterhub-k8s/jupyterhub/values.yaml

Lines 512 to 548 in 29f0adb

	image:
	# IMPORTANT: Bumping the minor version of this binary should go hand in
	# hand with an inspection of the user-scheduelr's RBAC
	# resources that we have forked in
	# templates/scheduling/user-scheduler/rbac.yaml.
	#
	# Debugging advice:
	#
	# - Is configuration of kube-scheduler broken in
	# templates/scheduling/user-scheduler/configmap.yaml?
	#
	# - Is the kube-scheduler binary's compatibility to work
	# against a k8s api-server that is too new or too old?
	#
	# - You can update the GitHub workflow that runs tests to
	# include "deploy/user-scheduler" in the k8s namespace report
	# and reduce the user-scheduler deployments replicas to 1 in
	# dev-config.yaml to get relevant logs from the user-scheduler
	# pods. Inspect the "Kubernetes namespace report" action!
	#
	# - Typical failures are that kube-scheduler fails to search for
	# resources via its "informers", and won't start trying to
	# schedule pods before they succeed which may require
	# additional RBAC permissions or that the k8s api-server is
	# aware of the resources.
	#
	# - If "successfully acquired lease" can be seen in the logs, it
	# is a good sign kube-scheduler is ready to schedule pods.
	#
	name: registry.k8s.io/kube-scheduler
	# tag is automatically bumped to new patch versions by the
	# watch-dependencies.yaml workflow. The minor version is pinned in the
	# workflow, and should be updated there if a minor version bump is done
	# here. We aim to stay around 1 minor version behind the latest k8s
	# version.
	#
	tag: "v1.28.13" # ref: https://github.com/kubernetes/kubernetes/tree/master/CHANGELOG

[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.' (scheduler: remove deprecated v1beta3 KubeSchedulerConfiguration component config kubernetes/kubernetes#119994, @SataQiu)
• The kube-scheduler selectorSpread plugin has been removed, please use the podTopologySpread plugin instead. (Remove deprecated selectorSpread kubernetes/kubernetes#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. (kubernetes/kubernetes#124500, @carlory) [SIG Scheduling and Storage]

API changes

• Fixed incorrect "v1 Binding is deprecated in v1.6+" warning in kube-scheduler log. (api: revert deprecation annotation for v1 Binding kubernetes/kubernetes#125540, @pohly) [SIG API Machinery]