Expo config loader fails during fingerprinting on Windows #3672

Problem

On Windows, every stim android run of an Expo app printed Cannot get Expo config from an Expo project from @expo/fingerprint's ExpoConfigLoader. Builds still succeeded, but the fingerprint is then computed without the app config. That can make cache keys miss changes to app.json or config plugins on Windows.

Evidence

Seen on every run while verifying #3669 and #3640 on windows-latest runners (trailhead, Expo SDK 58). During #3640, a pnpm node.exe shim first on PATH broke Node IPC and made Expo's config loader fail, which surfaced as fingerprint-mismatch on a Windows build worker. With the real Node first on PATH, the build worked, but this warning may have the same cause or a different one.

Cause

Unknown. Possible causes: the version-manager node.exe shim on PATH, or how the fingerprint subprocess is spawned on Windows.

Fix idea

Reproduce on a windows-latest runner with the real Node first on PATH and without any shim. If the warning remains, capture the loader's error, and compare the fingerprint with the macOS one for the same commit.