fix(js): handle npm 11 warnings in stderr during registry version resolution

npm 11+ (bundled with Node 24.3) writes deprecation warnings about unknown
environment configurations to stderr even when commands succeed. The registry
version resolver was incorrectly rejecting any npm view command with stderr
content, causing e2e tests to fail with Node 24.3.

This change updates the error handling to only reject on actual errors,
ignoring npm warning messages that start with 'npm warn'.

Author: ndcunningham

packages/js/src/release/version-actions.ts

@@ -111,7 +111,15 @@ export default class JsVersionActions extends VersionActions {
             if (error) {
               return reject(error);
             }
-            if (stderr) {
+            // Only reject on stderr if it contains actual errors, not just npm warnings
+            // npm 11+ writes "npm warn" messages to stderr even on successful commands
+            if (
+              stderr &&
+              !stderr
+                .trim()
+                .split('\n')
+                .every((line) => line.startsWith('npm warn'))
+            ) {
               return reject(stderr);
             }
             return resolve(stdout.trim());