New k8s CRI API: image_id in PullImageResponse

### What is the problem you're trying to solve

The `PullImageResponse` message of the Kubernetes CRI API was updated to include `image_id`, which is designed to formalize the image identifier across CRI API messages.

This means that the value of image identifier fields across different CRI API messages MUST always be the same as long as it refers to the same image.
See https://github.com/kubernetes/kubernetes/pull/137217 for more information on the affected fields.

### Describe the solution you'd like

Include `image_id` in CRI API's `PullImageResponse`

### Additional context

This change happened because we recently identified that the `image_ref` field was not filling the role of a unique image ID properly due to its vague definition.
Even though in containerd this works fine, we would like to make sure we have a stable identifier that we can use for each container runtime. This does not mean that identifiers must be the same across all runtimes - the stable identifier rule only applies within each of the runtimes.