test: Add network policy enforcement tests

Add comprehensive NetworkPolicy tests for kube-apiserver and
kube-apiserver-operator namespaces. Tests verify policy creation,
reconciliation, and enforcement including default-deny and allow
rules patterns.

Signed-off-by: Kaleemullah Siddiqui <ksiddiqu@redhat.com>

Author: kaleemsiddiqu

cmd/cluster-kube-apiserver-operator-tests-ext/main.go

@@ -66,7 +66,7 @@ func prepareOperatorTestsRegistry() (*oteextension.Registry, error) {
 	registry := oteextension.NewRegistry()
 	extension := oteextension.NewExtension("openshift", "payload", "cluster-kube-apiserver-operator")
 
-	// The following suite runs tests that verify the operator’s behaviour.
+	// The following suite runs tests that verify the operator's behaviour.
 	// This suite is executed only on pull requests targeting this repository.
 	// Tests tagged with both [Operator] and [Serial] are included in this suite.
 	extension.AddSuite(oteextension.Suite{
@@ -77,6 +77,17 @@ func prepareOperatorTestsRegistry() (*oteextension.Registry, error) {
 		},
 	})
 
+	// The following suite runs tests that verify the operator's behaviour.
+	// This suite is executed only on pull requests targeting this repository.
+	// Tests tagged with [Parallel] and [Operator] are included in this suite.
+	extension.AddSuite(oteextension.Suite{
+		Name:        "openshift/cluster-kube-apiserver-operator/operator/parallel",
+		Parallelism: 1,
+		Qualifiers: []string{
+			`!name.contains("[Serial]") && name.contains("[Operator]")`,
+		},
+	})
+
 	specs, err := oteginkgo.BuildExtensionTestSpecsFromOpenShiftGinkgoSuite()
 	if err != nil {
 		return nil, fmt.Errorf("couldn't build extension test specs from ginkgo: %w", err)