cri: drive the server with Kubernetes' own cri-api client
Mirror the etcd clientv3 interop for CRI: test/criclient drives our server with
k8s.io/cri-api (the kubelet's RuntimeService/ImageService client) as the oracle,
over the standard CRI unix socket. run.sh runs two phases:
1. cri-api client -> crictd (the in-memory fake server)
2. cri-api client -> crict-proxy (the transparent allow_all proxy) ->
crictd, or a real runtime via UPSTREAM=<sock> (e.g. containerd)
covering Version/Status, the pod+container lifecycle (run/create/start/status/
list/stop/remove) and the image lifecycle (pull/list/status/remove). Both phases
pass, proving the fake and the proxy are wire-conformant with the real client.
Gated behind CRI_LIVE=1 (dune @criclient alias), SKIPs without a Go toolchain --
the same shape as the existing critest interop.