feat: remove cluster wide permission objects

Kubevirt-tekton-tasks does not need to ship additional
service accounts, role bindings and cluster roles, because
if no service account is provided, tekton uses default SA
pipeline, which is available in almost all namespaces and already
has all necessary permission. This change will allow non
privilidged user to run tasks without need admin permissions.
The permission objects will remain only in README of each task
so user can easily make it work if user will need multinamespace
functionality.

This PR adjusts testing framework + all affected scripts
Signed-off-by: Karel Simon <[email protected]>

.github/workflows/test-yaml-consistency.yaml

@@ -0,0 +1,15 @@
+name: test yaml consistency
+
+on:
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v4
+    - name: test yaml consistency
+      run: scripts/test-yaml-consistency.sh

automation/e2e-tests.sh

@@ -11,7 +11,8 @@ export NUM_NODES=${NUM_NODES:-2}
 
 ./automation/e2e-deploy-resources.sh
 
-kubectl get namespaces -o name | grep -Eq "^namespace/$DEPLOY_NAMESPACE$" || kubectl create namespace "$DEPLOY_NAMESPACE"
+oc get namespaces -o name | grep -Eq "^namespace/$DEPLOY_NAMESPACE$" || oc create namespace "$DEPLOY_NAMESPACE"
+oc project "$DEPLOY_NAMESPACE"
 
 if [[ "$DEV_MODE" == "true" ]]; then
   make cluster-sync