What is the problem you're trying to solve
When CRI-O* tries to start a container using shim v2, it may simply fail if the runtime specified is not part of the PATH (even if the full binary path is specified).

*: Yes, CRI-O, as CRI-O vendors this code. :-)

Describe the solution you'd like
I'd like to see the full binary path taken into consideration.

Additional context
Please, take a look at:

• CRI-O issue: runtimeVM: containerd-shim-kata-v2 binary can't be load from an arbitrary path cri-o/cri-o#4541
• Kata Containers issue: kata-deploy: CRI-O configuration doesn't work with shimv2 kata-containers/kata-containers#1357