How to configure cri-dockerd ImagePullProgressDeadline for large images

### Description

Hey, I have been using cri-dockerd with k8s using Colima (`--runtime docker`). cri-dockerd sometimes struggles to pull large images if they take longer than 1 minute to pull due to this setting here (docker images that take longer than 1m to pull will get stuck in ImagePullBackoff): https://github.com/Mirantis/cri-dockerd/blob/master/config/options.go#L45C4-L48

The easy fix for this in the past was to increase ImagePullProgressDeadline to 10 minutes. In the past I would have developers run this to apply the change (it just adds `--image-pull-progress-deadline 10m` to the list of arguments that cri-dockerd starts with and restarts it:

```bash
# replace command_args line and add --image-pull-progress-deadline
colima ssh -- sudo sed -i '/command_args/c command_args="--container-runtime-endpoint unix:///run/cri-dockerd.sock --image-pull-progress-deadline 10m"' /etc/init.d/cri-dockerd

# restart cri-dockerd
colima ssh -- sudo rc-service cri-dockerd restart
```

In the latest version of the Colima iso, `/etc/init.d/cri-dockerd` is gone and it doesn't look like `cri-dockerd` is managed by rc-service any more. How do I configure cri-dockerd to increase ImagePullProgressDeadline in the current version of Colima?

### Version

Colima Version: 0.5.5
Lima Version: 0.16.0
Qemu Version: 8.0.0

### Operating System

- [X] macOS Intel <= 12 (Monterrey)
- [X] macOS Intel >= 13 (Ventura)
- [X] macOS M1 <= 12 (Monterrey)
- [X] macOS M1 >= 13 (Ventura)
- [X] Linux

### Output of `colima status`

INFO[0000] colima is running using QEMU
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: 9p
INFO[0000] socket: unix:///Users/jstafford/.colima/default/docker.sock
INFO[0000] kubernetes: enabled

### Reproduction Steps

1. Start colima with: `colima start -k -r docker`
2. Pulling large images in Kubernetes results in ImagePullBackoff/ErrImagePull if the image can't be downloaded in the default time of 1 minute
3. `/etc/init.d/cri-dockerd` is no longer present in the colima iso image, so `cri-dockerd` can no longer be configured to increase the timeout to a more reasonable value.

### Expected behaviour

Hoping that you can either increase the default value of ImagePullProgressDeadline to 10m, or point me to how cri-dockerd can be configured in the current Colima version.

### Additional context

_No response_

Look at how cri-dockerd is configured in the current Colima setup, likely in the Lima VM configuration or systemd service files. Examine the Colima source code for runtime configuration, particularly around cri-dockerd startup. The goal is to add a configurable ImagePullProgressDeadline flag to the cri-dockerd arguments. Check for existing configuration templates or flags in the codebase that manage runtime options.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.