Fix the npm registry issue in release pipeline

[Deekshitha2812]

Problem

The node-api-release pipeline is failing due to 1ES Network Isolation (Enforce mode) blocking outbound connections:

1. NodeTool@0 step fails for Node 16.x, 18.x — Network Isolation blocks connections to nodejs.org, preventing Node binary downloads.
2. Upgrade npm step fails for Node 20.x, 22.x, 24.x — Network Isolation (CFSClean policy) blocks connections to registry.npmjs.org, preventing npm install -g npm@8.

Root Cause

• The pipeline's Network Isolation policy (Preferred,CFSClean) does not include the NodeTool shared policy, which is required to allow downloads from nodejs.org.
• The CFSClean policy intentionally blocks all public package registries (including registry.npmjs.org) for SFI compliance. The Upgrade npm step (npm install -g npm@8) attempts to download from registry.npmjs.org, which is blocked.

Fix

1. Added NodeTool to the network isolation policy — Allows nodejs.org access so NodeTool@0 can download Node binaries.
2. Made npm upgrade conditional — Instead of always running npm install -g npm@(npmversion) (which fails under CFSClean), the step now checks the bundled npm major version and only upgrades if below the required version. Uses --userconfig to read auth from the project .npmrc (set by NpmAuthenticate).
3. Upgraded NodeTool@0 to UseNode@1 — NodeTool@0 is deprecated; replaced with UseNode@1 (updated versionSpec → version input accordingly).

Testing

• Verified that the pipeline runs successfully with the NodeTool policy added and the Upgrade npm step removed.
  https://dev.azure.com/mseng/AzureDevOps/_build/results?buildId=31616938&view=results

[Deekshitha2812]

/azp run

[Deekshitha2812]

/azp run

[Deekshitha2812]

/azp run

[Deekshitha2812]

/azp run

[Deekshitha2812]

/azp run