[release/1.7] Add cri-api v1alpha2 usage warning to all api calls

[ruiwen-zhao]

Previous #9336 added warnings for the usage of cri-api Status and Version.

There are some use cases where clients might use cri-apis without calling those two apis. For example,

1. client uses crictl to pre-pull container images,
2. client uses ContainerStatus to find the container for a certain pid for monitoring purposes.

Therefore, this PR adds warning to all cri-api v1alpha2 apis.

[SergeyKanzhelev]

this LGTM. I don't know how big this problem will be for the end user - it may be interesting to log the specific call that was called. This way customers received this warning may understand who called it

[samuelkarp]

/cherrypick release/1.6

[k8s-infra-cherrypick-robot]

@samuelkarp: #9479 failed to apply on top of branch "release/1.6":

Applying: Add cri-api v1alpha2 usage warning to all api calls
Using index info to reconstruct a base tree...
A	pkg/cri/instrument/instrumented_service.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/cri/server/instrumented_service.go
CONFLICT (content): Merge conflict in pkg/cri/server/instrumented_service.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add cri-api v1alpha2 usage warning to all api calls
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release/1.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.