test/e2e: track the libvirt tests failing with cri-o

[wainersm]

Describe the bug

An outcome of #2068 (issue #1981) is the following tests failing:

TestLibvirtCreatePeerPodContainerWithExternalIPAccess
TestLibvirtPodToServiceCommunication
TestLibvirtPodsMTLSCommunication

TestLibvirtPodToServiceCommunication and TestLibvirtPodsMTLSCommunication fail with the same symptom: cannot access a service by name from within the container. Both are client/server test case style.

The TestLibvirtCreatePeerPodContainerWithExternalIPAccess fail because from the container it's not able to resolve the www.google.com address.

Worth noting:

1. @littlejawa was able to pass TestLibvirtPodToServiceCommunication on OCP 4.17 with OSC 1.17. It might indicate a problem on kubernetes setup on our e2e tests for libvirt, that leverages kcli
2. TestLibvirtPodToServiceCommunication, TestLibvirtPodsMTLSCommunication and TestLibvirtCreatePeerPodContainerWithExternalIPAccess fail on CI (running on github actions) even with containerd; however they pass when running on dev's workstation. Unlikely, with CRI-O, it fails on both scenarios.

How to reproduce

N/A

CoCo version information

N/A

What TEE are you seeing the problem on

None

Failing command and relevant log output

No response