Support calamari image volumes for Kubernetes script pods

[APErebus]

Background

We are implementing the ability for the Kubernetes agent to load and execute Calamari via a Kubernetes image volume.

This k8s feature loads an image as a read-only volume directly into the pod.

To do this, Octopus Server needs to send the calamari name (e.g. Calamari or Calamari.AzureAppService etc) and the version so that the correct container can be acquired.

Results

Adds a new property to StartKubernetesScriptCommandV1, CalamariImageConfiguration, which defines the Name and Version of the Calamari image to be loaded.

This feature requires Kubernetes 1.35 or newer (as that is when the ImageVolume feature gate was enabled by default).

It also needs to be explicitly enabled by default, via a helm chart value scriptPods.calamariImageVolume.enabled. The PR for the helm chart is OctopusDeploy/helm-charts#610

This is an example of what happens when you try and use the feature on a cluster with a version < 1.35

Related to MD-2016

How to review this PR

Verify/validate this is backwards compatible

Quality ✔️

Pre-requisites

• I have read How we use GitHub Issues for help deciding when and where it's appropriate to make an issue.
• I have considered informing or consulting the right people, according to the ownership map.
• I have considered appropriate testing for my change.

---

👨‍💻 Written by a human without AI

[Jtango18]

This looks pretty straight forward. Were there additional changes requried for Calamari to make this work?

[APErebus]

This looks pretty straight forward. Were there additional changes requried for Calamari to make this work?

Only the creation of the docker images, which is in main

[flin-8]

LGTM