chore(release): bump example and helm image tags to 0.4.0

[saturley-hall]

Summary

Release housekeeping for the release/0.4.0 branch — bumps the modelexpress-server NGC image tag from 0.3.0 to 0.4.0 in places that were deferred until the release branch was cut.

Examples (6 manifests):

• examples/p2p_transfer_k8s/server/redis_backend/modelexpress-server-redis.yaml
• examples/p2p_transfer_k8s/server/kubernetes_backend/modelexpress-server-kubernetes.yaml
• examples/p2p_transfer_k8s/client/trtllm/mx-infra-decode.yaml
• examples/dynamo_p2p_transfer_k8s/vllm/vllm-multi-node-aggregated.yaml
• examples/dynamo_p2p_transfer_k8s/vllm/vllm-single-node-disaggregated.yaml
• examples/dynamo_model_cache_k8s/agg.yaml

Helm (5 files):

• helm/values.yaml, helm/values-development.yaml, helm/values-production.yaml, helm/test-values.yaml — default image.tag
• helm/README.md — default-tag column + a docker pull example

helm/Chart.yaml was already on 0.4.0; only the image-tag defaults inside the values*.yaml files were stale.

Out of scope (flagged but intentionally not bumped):

• vllm-runtime:1.0.1 in examples/dynamo_p2p_transfer_k8s/Dockerfile is older than the 1.1.x used elsewhere — that's a separate compatibility decision, not MX 0.4.0 housekeeping.
• Other non-MX pins (redis:7-alpine, python:3.11-slim, curlimages/curl:8.9.1, EFA 3.0.0g, vLLM 0.18.0 mentions) — left alone.
• Cargo crate versions in ATTRIBUTIONS_Rust.md that incidentally contain 0.3.0 — unrelated.
• One CI manifest comment that explicitly contrasts against nvcr.io/0.3.0 — bumping would invert the meaning.

Test plan

• grep -rn "modelexpress-server:0\.3\.0" . returns zero hits.
• grep -rn "tag: \"0\.3\.0\"" helm/ returns zero hits.
• Smoke-deploy with helm install … helm/ and confirm the 0.4.0 image pulls (will require nvcr auth).

🤖 Generated with Claude Code