The rationale to test criu-dev is at #3116. If we remove it, we'll have to deal with the future breakage after a new criu release. Now we can see issues before it is released.

I agree, though one thing to note is that in #3116 the CI job was not required for PRs to be merged, but since we switched to the complete setup for marking required jobs, it has become required. Any ideas of how we might deal with this? (I guess a re-usable workflow is the most GHA-friendly solution...)

CRIU issue is now fixed (see checkpoint-restore/criu#2781, checkpoint-restore/criu#2819). Alas, we have a different CI failure now (#5010) which for some reason happens with criu-dev but I can't see why.

Guess we can close this PR. I opened #5012 to make criu-dev "optional".