fix(windows): make node-pty compat shim adaptive

[web3dev1337]

Summary

• make the Windows node-pty runtime shim try the native 7-argument startProcess call first
• only retry without the 7th useConptyDll argument when the native binding throws the startProcess usage error
• expand nodePtyCompat unit coverage to lock both working Windows source builds and stale packaged bindings

Why

The current runtime shim on main always drops the 7th argument for node-pty@1.2.0-beta.12. That rescues stale packaged bindings, but it breaks normal Windows source/test environments whose native module already expects all 7 arguments. That is what failed in the merged #974 Windows/unit run.

Verification

• npm run test:unit -- tests/unit/nodePtyCompat.test.js tests/unit/sessionManager.windowsPty.test.js tests/unit/commanderService.windowsShellArgs.test.js
• npm run test:unit