Self-managed NVCT tasks use the function ICMS request action

[sbaum1994]

Why

A container task launched through the self-managed NVCT API remains queued because its compute-plane ICMSRequest is created with the function action RequestICMSInstances. NVCA follows the function path, creates zero task instances, and repeatedly reports that zero of one requested instances were created.

This was reproduced with SIS chart 2.0.0, NVCT chart 1.4.3, and NVCA 3.2.7 while validating #861.

Expected behavior

NVCT task requests reach NVCA as RequestICMSInstancesForTask, or NVCA otherwise identifies the populated task details and task launch specification as a task request. The task pod should be created without editing the live custom resource.

Reproduction

1. Install the local multi-cluster self-managed Helmfile feature.
2. Run tests/bdd/scripts/run-nvct-task-smoke.sh.
3. Inspect the generated ICMSRequest in namespace nvcf-backend.
4. Observe spec.action: RequestICMSInstances and no task pod.
5. Change only spec.action to RequestICMSInstancesForTask; NVCA creates the pod and the task completes.

Acceptance criteria

• NVCT container tasks generate the task ICMS request action.
• No manual custom-resource edit is required.
• TestMultiClusterHelmfile passes from a clean topology.

Parent: #858