gha: k8s: Stop running kata-deploy tests as part of the k8s suite

In a follow-up series, we'll add a whole suite for the kata-deploy
tests.  With this in mind, let's already get rid of this one and avoid
more kata-deploy tests to land here.

Fixes: #7642

Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>

tests/integration/kubernetes/kata-deploy-ensure-runtimec-classes-created.bats

@@ -1,38 +0,0 @@
-#!/usr/bin/env bats
-#
-# Copyright (c) 2023 Intel Corporation
-#
-# SPDX-License-Identifier: Apache-2.0
-#
-
-load "${BATS_TEST_DIRNAME}/../../common.bash"
-load "${BATS_TEST_DIRNAME}/tests_common.sh"
-
-setup() {
-	# We expect 2 runtime classes because:
-	# * `kata` is the default runtimeclass created, basically an alias for `kata-${KATA_HYPERVISOR}`.
-	# * `kata-${KATA_HYPERVISOR}` is the other one
-	#    * As part of the tests we're only deploying the specific runtimeclass that will be used, instead of all of them.
-	expected_runtime_classes=2
-
-	# We expect both runtime classes to have the same handler: kata-${KATA_HYPERVISOR}
-	expected_handlers_re=( \
-		"kata\s+kata-${KATA_HYPERVISOR}" \
-		"kata-${KATA_HYPERVISOR}\s+kata-${KATA_HYPERVISOR}" \
-	)
-}
-
-@test "Test runtimeclasses are being properly created" {
-	# We filter `kata-mshv-vm-isolation` out as that's present on AKS clusters, but that's not coming from kata-deploy
-	current_runtime_classes=$(kubectl get runtimeclasses | grep -v "kata-mshv-vm-isolation" | grep "kata" | wc -l)
-	[[ ${current_runtime_classes} -eq ${expected_runtime_classes} ]]
-
-	for handler_re in ${expected_handlers_re[@]}
-	do
-		[[ $(kubectl get runtimeclass | grep -E "${handler_re}") ]]
-	done
-}
-
-teardown() {
-	kubectl get runtimeclasses
-}

tests/integration/kubernetes/run_kubernetes_tests.sh

@@ -18,7 +18,6 @@ if [ -n "${K8S_TEST_UNION:-}" ]; then
 	K8S_TEST_UNION=($K8S_TEST_UNION)
 else
 	K8S_TEST_UNION=( \
-		"kata-deploy-ensure-runtimec-classes-created.bats" \
 		"k8s-attach-handlers.bats" \
 		"k8s-caps.bats" \
 		"k8s-configmap.bats" \