Document how the shim expects to have information configured on a container

[kate-goldenring]

Sometimes SpinKube users may prefer to skip using the Spin Operator and choose to define their own K8s deployments, for example if using Argo Rollout resources. We should document how the Shim expects information such as OTEL parameters, etc to be passed inside PodSpecs (usually as Container environment variables) to make it easier for users to construct their own deployments.

[bacongobbler]

I could see this being written two separate ways:

1. A guide on integrating (parts of) SpinKube with other tools like ArgoCD.
2. A topic guide on using containerd-shim-spin in a non-SpinKube environment.

Which would be more appropriate here? One approach is inward-facing (shim docs), the other is outward-facing (integration with argocd).

[kate-goldenring]

I think those both sound great. The second is probably quicker to tackle.