Resolve GitHub actions workflow warnings

[austinvazquez]

Small CI updates to run cri-o tests on Ubuntu 22.04 to resolve warnings in GitHub actions workflows.

Also updated containerd/project-checks to latest @v1 will not grab latest in this case because containerd/project-checks has v1 tag.

Signed-off by: Austin Vazquez macedonv@amazon.com

[ktock]

@austinvazquez Thank you for the patches.

cri-o tests on Ubuntu 22.04

IIRC CRI-O tests fail on ubuntu:22.04 runner because of "CRI-O in Docker" issue (discussed in #622 )
Could you separate this commit into another PR if this commit doesn't pass the CI as of now?

containerd/project-checks to latest @ v1

Thanks!

[ktock]

https://github.com/containerd/stargz-snapshotter/actions/runs/3585033772/jobs/6032487166#step:3:575

 #11 30.71 github.com/containerd/containerd/cmd/containerd imports
#11 30.71 	github.com/containerd/stargz-snapshotter/service/plugin imports
#11 30.71 	k8s.io/cri-api/pkg/apis/runtime/v1alpha2: package k8s.io/cri-api/pkg/apis/runtime/v1alpha2 provided by k8s.io/cri-api at latest version v0.25.4 but not at required version v0.26.0-beta.0

This will be fixed in #1011

[austinvazquez]

IIRC CRI-O tests fail on ubuntu:22.04 runner because of "CRI-O in Docker" issue (discussed in #622 ) Could you separate this commit into another PR if this commit doesn't pass the CI as of now?

Thanks for the heads up @ktock . I was thinking maybe perhaps it was a runc version mismatch but that seems to not be the case. I'll close and split the commits.