Add a new CI job equivalent to https://github.com/kata-containers/kata-containers/blob/main/.github/workflows/run-kata-coco-tests.yaml#L232 but having k8s configured with CRI-O.

The current job tests kata on AKS with containerd. One first thing to check is whether AKS can be configured with CRI-O or not. If not then we can consider running a test with k0s just like (https://github.com/kata-containers/kata-containers/blob/main/.github/workflows/run-k8s-tests-with-crio-on-garm.yaml).

It will be needed to adapt at least the registry authentication test as it setup secret that isn't need for CRI-O (https://github.com/kata-containers/kata-containers/blob/main/tests/integration/kubernetes/k8s-guest-pull-image-authenticated.bats#L33). We should check all the CoCo specific tests actually, as they add annotations and may do other things specifics of containerd/nydus-snapshotter