libvirt: run CI for k8s configured with CRI-O

[wainersm]

Recently kata-deploy got support for configuring CRI-O to do guest-pull (kata-containers/kata-containers#9537), and finally CRI-O was added on CoCo operator (confidential-containers/operator#376).

The current CI jobs (on pull and daily) for libvirt are all testing k8s configured with containerd. This issue is to track the work required to test with CRI-O as well.

It seems the major changes will be:

• Adapt kcli_cluster.sh to configure the cluster with CRI-O
• The container runtime (containerd or cri-o) should be passed to the libvirt's cluster provisioner via properties
• Convert e2e_libvirt.yaml workflow to matrix of jobs with entries for cri-o and containerd