image-pull: add e2e execution time plot

[csegarragonz]

The idea is to compare the execution time of SC2 with different image-pulling configurations:

• Guest pull (regular)
• Lazy guest pull (w/ nydus)
• Host mount (w/ nydus)
• Hybrid

Do for two different applications: helloworld-py and some tflite inference.

Here we should also analyze the situation where we pull the image twice in the guest and in the host:

(From CNCF Slack)
The containerd shim API is modelled after the OCI runtime spec, with a few extras. Notably, it deals with bundles instead of images. Since containerd does not know that the bundle is going to be unused by the runtime, it always needs to prepare it. Now, if containerd was using the snapshotter without inspecting the committed snapshots, we could theoretically not materialize anything and get away with it.
However, since the CRI deals with images, containerd needs to translate between image and bundle. Due to unfortunate design choices (edit: in the OCI image spec, which was informed by the Docker image spec), some of this translation involves looking up content in the bundle - one example I know is the mentioned named user lookup (see #9928). (