fix: preserve process.cwd() after SETLOCAL in cmd shims

[dyk1454683243-sudo]

Fixes #69

Cause

Shebang .cmd shims isolate _prog with SETLOCAL, then launch Node with:

endLocal & goto #_undefined_# 2>NUL || title %COMSPEC% & "%_prog%" ...

goto #_undefined_# is the existing “Terminate Batch Job?” workaround: it leaves batch context so Node is not a child of the .cmd. Leaving that context implied-ENDLOCALs leftover frames.

SETLOCAL saves the current directory as well as the environment. The issue’s parent script is:

setlocal
cd C:\abcdefg\
test.cmd
endlocal

When the shim exits batch context, the parent setlocal is popped too, so the cd is undone and Node’s process.cwd() is the pre-cd directory. Same-line %CD% is still the post-cd path, because cmd.exe expands percents before any command on the line runs.

This is still the generated launch line on current main. No open PR already claimed #69.

Fix

After the goto, re-apply the already-expanded directory:

endLocal & goto #_undefined_# 2>NUL || title %COMSPEC% & cd /d "%CD%" & set PATHEXT=... & "%_prog%" ...

cd has to come after goto. A restore before the goto is undone by the implied ENDLOCAL.

• Keeps SETLOCAL and the goto trick (Ctrl+C / issue Invocation fails if %0 is "prog" instead of "path\to\prog" and prog was quoted when invoked #10 / cli#969)
• No-shebang shims are unchanged (they never used this launch line)
• Parent env vars set after setlocal (e.g. JAVA_HOME in On windows generated *.cmd file overwrites console window title  cli#4239) are a separate problem and are not addressed here

Tests

• Reproduces the issue’s .cmd / SETLOCAL / :find_dp0 / parent setlocal+cd pattern: without cd /d "%CD%" the simulated Node cwd is the pre-cd directory; with it, cwd is C:\abcdefg
• Generated shebang shims must contain cd /d "%CD%" after goto #_undefined_#
• Windows-only functional test: parent test.bat does setlocal + cd + shim; aaaa.js writes process.cwd() (skipped on non-Windows CI)
• Snapshots updated

[dyk1454683243-sudo]

Withdrawing this PR while I clean up a high-volume open-PR backlog. Sorry for the noise — happy to come back later with a focused change if useful.