fix(package-env): improve Windows npm version detection

[billxinli]

Attempting to fix a bug where Socket CLI fails to detect npm version (socket optimize blocked) on windows.

Windows 11 + Powershell

Windows 11 + cmd

OSX

---

Note

Strengthens npm version detection on Windows to handle shims and JS entrypoints reliably.

• Add preferWindowsCmdShim to select .cmd shims and use when resolving npm path
• Use resolveBinPathSync in getAgentVersion to detect JS entrypoints (.js/.cjs/.mjs) and execute via node; otherwise spawn directly with shell: WIN32
• Update getAgentExecPath for npm to prefer .cmd next to node.exe and handle shim replacement
• Add test/package-environment.npm-version.test.mts with Vitest cases for JS entrypoint execution, fallback on resolution failure, and non-JS executables

^{Written by Cursor Bugbot for commit d245ebd. Configure here.}

[jdalton]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no bugs!

---

Comment @cursor review or bugbot run to trigger another review on this PR