ci: k8s 1.30 tests are excluded for release-v3.11

[iPraveenParihar]

k8s 1.30 tests are excluded for release-v3.11 here

ceph-csi/.github/workflows/pull-request-commentor.yaml

Lines 23 to 32 in 4c7d419

	exclude:
	# the next Ceph-CSI version will not be tested with old Kubernetes
	- k8s: "1.26"
	branch: "release-v3.11"
	- k8s: "1.26"
	branch: "devel"
	# Ceph-CSI <= 3.11 was released before Kubernetes 1.30
	- k8s: "1.30"
	branch: "release-v3.11"

but mergify has status check condition for k8s 1.30 tests

ceph-csi/.mergify.yml

Lines 29 to 49 in 4c7d419

	- and:
	- base~=^(release-.+)$
	- "status-success=codespell"
	- "status-success=multi-arch-build"
	- "status-success=go-test"
	- "status-success=golangci-lint"
	- "status-success=mod-check"
	- "status-success=lint-extras"
	- "status-success=ci/centos/k8s-e2e-external-storage/1.27"
	- "status-success=ci/centos/k8s-e2e-external-storage/1.28"
	- "status-success=ci/centos/k8s-e2e-external-storage/1.29"
	- "status-success=ci/centos/k8s-e2e-external-storage/1.30"
	- "status-success=ci/centos/mini-e2e-helm/k8s-1.27"
	- "status-success=ci/centos/mini-e2e-helm/k8s-1.28"
	- "status-success=ci/centos/mini-e2e-helm/k8s-1.29"
	- "status-success=ci/centos/mini-e2e-helm/k8s-1.30"
	- "status-success=ci/centos/mini-e2e/k8s-1.27"
	- "status-success=ci/centos/mini-e2e/k8s-1.28"
	- "status-success=ci/centos/mini-e2e/k8s-1.29"
	- "status-success=ci/centos/mini-e2e/k8s-1.30"
	- "status-success=ci/centos/upgrade-tests-cephfs"

need to be fixed in separate PR.

for now will trigger manually k8s 1.30 tests, hopefully it should go through🤞

cc @Madhu-1 @Rakshith-R