CI: revisit the configurations tested

[wainersm]

This issue is meant to discuss and re-validate the current configurations we have CI jobs for.

To discuss:

• where we can increase the coverage?
  • cri-o support recently added (Improve cri-o support by using pull_type #376)
  • kata-remote hypervisor (CI: add operator tests job for peer-pods #336)
• What configurations we can drop?
  • example: should we still test on older than 1.7 containerd (ubuntu 20.04)?
• What configuration we should replace?
  • example: could we use qemu-coco-dev instead of qemu on non-tee jobs?

Here is the current matrix of jobs vs configuration:

Index	TEE	OS	ARCH	container runtime	Hypervisor	Keep (o) / Add (+) / Remove (-)	Notes
1	Non-TEE	Ubuntu 22.04	s390x	containerd	qemu	o	Plans to qemu-se? what about cri-o?
2	Non-TEE	Ubuntu 20.04	x86_64	containerd	qemu	-	Used to test upgrade of containerd 1.6 -> 1.7
3	Non-TEE	Ubuntu 22.04	x86_64	containerd	qemu	o	Replace to qemu-coco-dev? or add new?
4	Non-TEE	Ubuntu 22.04	x86_64	cri-o	qemu	+	Replace to qemu-coco-dev? or add two new?
5	TDX	Ubuntu 24.04	x86_64	containerd	qemu-tdx	o	Need new with cri-o?
6	SEV	Ubuntu 22.04	x86_64	containerd	qemu-sev	o	Need new with cri-o?
7	SNP	Ubuntu 22.04	x86_64	containerd	qemu-snp	o	Need new with cri-o?
8	Non-TEE	Ubuntu 22.04	x86_64	containerd	remote	+	Covered on peer pods somehow
9	Non-TEE	Ubuntu 22.04	x86_64	cri-o	remote	+	To be added on peer pods so covered somehow