Add retry to NuGet setup tasks for node24 task-host libuv crash

[dcristoloveanu]

Summary

Add retryCountOnTaskFailure: 3 to the two Node-handler setup tasks in this template (NuGetAuthenticate@1 and NuGetToolInstaller@1).

Why

Node 24 task-host wrappers on Windows ADO agents intermittently abort with Exit code 57005 (Watson bucket FAIL_FAST_FATAL_APP_EXIT_c0000409, faulting in vss-agent\externals\node24\bin\node.exe). Symbolicated against the Node 24.13.0 PDB, the stack ends in:

Assertion failed: !(handle->flags & UV_HANDLE_CLOSING)
file deps/uv/src/win/async.c, line 76

…which is libuv's uv_async_send() invoked from Node's WorkerThreadsTaskRunner::DelayedTaskScheduler shutdown path -- a lifecycle race between the task host's V8 platform tear-down and an in-flight async wakeup.

References:

• Upstream issue: libuv assertion on Windows with Node.js 23.x nodejs/node#56645 (open since 2025-01-17)
• Upstream fix PR: src: fix libuv assertion on windows nodejs/node#61999 (not merged as of writing)
• Agent issue: [BUG]: Sporadic task / step failures relating to usage of Node V24 and timer assertion errors microsoft/azure-pipelines-agent#5498 (open, no fix)

The agent ships Node 24 (externals/node24) regardless of any pipeline UseNode@1 step -- the task-host runtime is selected purely from each task's target.runtimeVersion. The only currently available mitigation for consumers is to retry the affected wrapper invocations.

In Azure-MessagingStore we measured ~9 NuGetAuthenticate@1 / Npm@1 / UseNode@1 crashes across ~99 builds in the past 7 days (per-task failure rate ~9%). With retryCountOnTaskFailure: 3 the residual rate drops to <0.01%.

Why this is safe

• NuGetAuthenticate@1 is idempotent (env-var setup + credential-provider probe).
• NuGetToolInstaller@1 is idempotent (downloads + caches nuget.exe); already had continueOnError: true.
• Retry triggers on any non-zero exit, but for these setup tasks the only meaningful "real" failures will simply re-fail through all 3 attempts and surface as before.

Rollback

Revert this commit once nodejs/node#61999 merges, Node ships it in a 24.x, the agent bumps NODE24_VERSION to that release, and the 1ES Hosted pool image rolls forward.