Running nvproxy containers without Docker

### Description

Opening this mostly to avoid spending too much time reverse engineering Docker, runc, nvidia-container-runtime and gVisor behaviors. 😄

Since we don't use Docker to run our containers, figuring out how runsc and nvidia-container-runtime hooks interact is a bit of a challenge. I've read through the nvproxy sandbox setup code, which got me the basic `nvidia-smi` tool to work with our runtime by brute-forcing the OCI config and the `--nvproxy` and `--nvproxy-docker` flags, but I've also managed to busy loop the gofer at one point somehow (server load over 3000) trying to just start one of our inferencing workloads.

Would there be any resources you would be willing to share about how this works under the hood? All the documentation I can find is mostly just "how to configure Docker/Kubernetes to expose GPUs", which doesn't go into those details.

### Is this feature related to a specific bug?

_No response_

### Do you have a specific solution in mind?

_No response_