fix(cli): use platform-specific PATH separator in npm tests

Fix npm ENOENT errors on Windows by using the correct PATH separator.
Windows uses semicolon (;) while Unix uses colon (:).

This caused npm to not be found in PATH on Windows CI, resulting in
"spawn npm ENOENT" errors in socket-npm-integration.test.mts.

Author: jdalton

packages/cli/src/commands/npm/socket-npm-integration.test.mts

@@ -39,6 +39,8 @@ if (!npmDirs.length) {
 
     describe(`Socket npm wrapper for ${npmDir}`, () => {
       const useDebug = isDebug('stdio')
+      // Use platform-specific path separator for PATH construction.
+      const pathSep = process.platform === 'win32' ? ';' : ':'
 
       it(
         'should intercept npm commands and show Socket output',
@@ -62,7 +64,7 @@ if (!npmDirs.length) {
                 cwd: npmPath,
                 env: {
                   ...process.env,
-                  PATH: `${npmBinPath}:${ENV.PATH}`,
+                  PATH: `${npmBinPath}${pathSep}${ENV.PATH}`,
                 },
               },
             )
@@ -105,7 +107,7 @@ if (!npmDirs.length) {
                 cwd: path.join(npmFixturesPath, 'lacking-typosquat'),
                 env: {
                   ...process.env,
-                  PATH: `${npmBinPath}:${ENV.PATH}`,
+                  PATH: `${npmBinPath}${pathSep}${ENV.PATH}`,
                 },
               },
             )