chore(ci): freeing up resources to run e2e tests on nested clusters

[universal-itengineer]

Description

To successfully run e2e tests in nested clusters, the cluster must have sufficient resources. Therefore, before deploying nested clusters, some virtual machines must be shut down to free up resources.
In the nightly-e2e-* and static-cse namespaces, virtual machines will not be shut down.
Also exclude VMs with label e2e-cluster/do-not-stop-vm-on-e2e-run

Turning off virtual machines is done by setting the runPolicy parameter to AlwaysOff

kubectl patch vm -n "$ns" "$name" --type=merge -p '{"spec":{"runPolicy":"AlwaysOff"}}'

Why do we need it, and what problem does it solve?

To successfully pass e2e tests on nested clusters, free resources are needed in the cluster.

What is the expected result?

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: ci
type: chore
summary: freeing up resources to run e2e tests on nested clusters