fix(llm-routing): consume scheme-aware Pylon and NVCA releases

[sbaum1994]

Problem

The self-managed stack uses a plaintext in-cluster Stargate registration endpoint and authenticated reverse QUIC. Current Pylon and NVCA releases can apply the reverse-QUIC trust bundle as a gRPC certificate authority even when the registration endpoint uses explicit HTTP. Worker registration then fails.

Issue #1367 tracks the paired source fix. Both components need released artifacts before the stack can consume the corrected contract. PR #1363 currently carries a temporary Pylon 0.13.0 pin only to keep the new smoke coverage running while these fixes are separated.

Scope

• Publish a Pylon release containing the scheme-aware gRPC CA selection fix from fix(llm-routing): keep plaintext gRPC independent of QUIC trust #1367.
• Publish an NVCA release that only injects a gRPC CA for HTTPS Stargate addresses.
• Update the self-managed control-plane Pylon version.
• Update the compute-plane NVCA version.
• Remove the temporary Pylon downgrade from test(bdd): add autoscaler and vanity smoke coverage #1363.
• Update the version catalog and generated artifact manifest.
• Rerun the self-managed LLM, autoscaler, and Vanity Gateway smoke coverage.

Definition of done

• Fixed Pylon and NVCA images are available from the supported registry.
• Plaintext in-cluster registration works without a gRPC CA override.
• HTTPS registration still uses the configured trust bundle.
• Reverse QUIC continues to authenticate with its transport trust bundle.
• The control-plane and compute-plane stacks consume the fixed releases.
• Documentation and the generated manifest report the fixed versions.
• Focused component tests and self-managed BDD smoke tests pass.

Blocked by #1367.
Related to #1361.

[sbaum1994]

Initial release check after #1372 merged:

• src/libraries/rust/stargate/v0.14.3 contains the Pylon scheme-aware gRPC trust fix.
• src/compute-plane-services/nvca/v3.3.0-dev.213 and .214 contain the NVCA half of the fix.
• The automated chart-version branch currently updates the NVCA operator chart to 3.3.0-dev.214.
• At the time of this check, nvcr.io/nvidia/nvcf/pylon:0.14.3 and nvcr.io/nvidia/nvcf/nvca:3.3.0-dev.214 do not have published manifests.

The GitHub release records are therefore not yet consumable artifacts. Keep the stack pins unchanged until supported registry images are available. Local k3d validation can use locally built images and explicit overrides without landing development-only pins in this issue's production change.