Ensure cgroups v1 CI coverage

[BenTheElder]

We had been using github actions to get some easy to setup coverage of cgroup v2 VMs, and later some other things like podman and nerdctl

Today cgroup v2 is the default in Kubernetes CI, so we need some coverage for cgroup v1.

cc @aojea @stmcginnis

We will need to re-evaluate the actions..

See also: #3915 for longer term

[BenTheElder]

context: kubernetes/k8s.io#5276

[aojea]

What remains using cgroupsv1 in the ecosystem?

Some links https://lpc.events/event/18/contributions/1807/

[BenTheElder]

What remains using cgroupsv1 in the ecosystem?

That sounds like a discussion for #3915
As long as we aren't moving forward on #3915 we should maintain some coverage, similar to when we had rootless and v2 while they were unusual.

Otherwise we should plan to drop it and remove the v1 hacks. But I don't think we're there yet, given our own CI only just switched. GKE switched by default for 1.33 which is still in rapid. Kubernetes also does not plan to drop it yet, only no new features.

[aojea]

It was mostly curiosity