Upgrade Grove to v0.1.0-alpha.12 and Dynamo Operator to 1.4.1 (fixes nvbug 6673896)

[estroz]

Summary

Upgrade Grove from v0.1.0-alpha.11 to v0.1.0-alpha.12, and Dynamo Operator from 1.2.1 to 1.4.1, in the self-hosted stack.

Root cause / breaking change

A topology-constrained multinode DynamoGraphDeployment failed admission on a cluster with:

no matches for kind "ClusterTopology" in version "grove.io/v1alpha1"

Grove renamed the ClusterTopology CRD to ClusterTopologyBinding in ai-dynamo/grove#616. The currently pinned Dynamo Operator (1.2.1) predates Dynamo's own migration to the ClusterTopologyBinding API, so its admission webhook still resolves the legacy ClusterTopology kind, which no longer exists on cluster.

Dynamo's v1.4.0 release notes confirm this directly:

Grove subchart/API dependency now requires v0.1.0-alpha.11 or later; v1.4.0 ships v0.1.0-alpha.12-rc1 (ClusterTopologyBinding API required). Migrate: Upgrade externally-installed Grove to >= v0.1.0-alpha.11 in lockstep with Dynamo, since older Grove releases using the ClusterTopology API are no longer compatible.

Bumping Dynamo Operator to 1.4.1 resolves the admission mismatch. Grove v0.1.0-alpha.12 also carries a second breaking change worth calling out:

• Mandatory one-time PodGang naming migration (legacy base/scaled naming to epoch-based PodGangMap), run automatically by the operator on startup. Running workloads are not disrupted per the grove release notes.

Scope

• bump deploy/stacks/nvcf-compute-plane/helmfile.d/01-dependencies.yaml.gotmpl pins for grove-operator and dynamo-operator.
• add ClusterTopologyBinding to the NVCA allowedExtraKubernetesTypes allowlist (currently missing entirely, gap unrelated to the rename itself).

Verification

• Local NCP cluster and unit testsing