Separate rancher from tested clusters

[kravciak]

Currently everything runs on the same VM:

• k3d cluster created in VM
• rancher installed on k3d cluster
• everything installed on local cluster
• tests running on the same VM

This sometimes leads to a problem, for example when kubewarden policies are changed it takes resources from local cluster and rancher is affected.

Look into the solution where rancher runs on it's own cluster. Tested clusters are either imported or created on demand.