Install crictl on the host as part of CRI binaries download

[Copilot]

crictl is missing from the host, making container runtime troubleshooting difficult. This adds it to the existing download-cri-binaries bootstrap step alongside containerd and runc.

Proto changes

• Added crictl_version to DownloadCRIBinariesSpec (field 3)
• Added crictl_download_url and crictl_path to DownloadCRIBinariesStatus (fields 5–6)
• Regenerated action.pb.go

Download logic (components/cri/v20260301/download.go)

Follows the same pattern as runc/containerd:

• defaultCrictlURLTemplate — cri-tools GitHub releases tar.gz (marked FIXME to confirm endpoint)
• downloadCrictl() — extracts crictl from the tar; returns an error if the binary is absent in the archive
• crictlVersionMatch() — idempotency check via crictl --version
• constructCrictlDownloadURL() — arch-aware URL construction

Config

• DefaultCrictlVersion = "1.33.0" added to pkg/config/defaults.go (marked FIXME to confirm version)
• CrictlConfig struct + Crictl CrictlConfig field added to Config, mirroring RuncConfig
• Bootstrapper wires cfg.Crictl.Version (with DefaultCrictlVersion fallback) into the spec builder

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Install crictl on the host</issue_title>
<issue_description>We should also include the crictl tool on the host for troubleshooting. This can be part of the cri binaries download task.</issue_description>

<agent_instructions>please start a minimal change for this. We will come back later and provide the correct values / endpoints</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Install crictl on the host #112

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.