fix(core): handle spaces when launching nxFork

[Cammisuli]

Current Behavior

When trying to call nxFork in a directory that has a space, script interpreters are unable to locate the file because it parses the space as a separate argument

Expected Behavior

We now wrap nxFork arguments that have a space with double quotes on unix, and use the GetShortPathNameW Windows API to get the directory short name in Windows.

The command that gets built for nxFork will look like these:

• Windows: node C:\dev\triage\TESTSP~1\NODE_M~1\nx\src\TASKS-~1\fork.js \\.\pipe\nx\C:\Users\jon\AppData\Local\Temp\b4f70514e449658222c6\fp11424.sock test:build:production
• Unix: node "/workspaces/test space/nx" /temp/f11424.sock test:build:production

Related Issue(s)

Fixes #21462

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Feb 2, 2024 11:14pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit c693cbf. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

🟥 Failed Commands
nx affected --target=e2e --base=cb3da6c244ad694189bc88610ef7d7ba7ee5b9df --head=c693cbf69ca0d70e0044365f6f0ef499352f2d0c --parallel=1

✅ Successfully ran 5 targets

• nx affected --targets=lint,test,build --base=cb3da6c244ad694189bc88610ef7d7ba7ee5b9df --head=c693cbf69ca0d70e0044365f6f0ef499352f2d0c --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=cb3da6c244ad694189bc88610ef7d7ba7ee5b9df --head=c693cbf69ca0d70e0044365f6f0ef499352f2d0c
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=cb3da6c244ad694189bc88610ef7d7ba7ee5b9df --head=c693cbf69ca0d70e0044365f6f0ef499352f2d0c

---

Sent with 💌 from NxCloud.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.