Windows prepare npm@latest --activate times out.

Corepack on Windows inside of GitHub Actions appears to fail prepare npm@latest --activate the first time it is invoked for some reason. Subsequent calls to prepare npm@latest --activate (appear to) succeed.

This is with npm install -g corepack@latest, so it fails in the most-recent version.

I'm unable to reproduce the failure locally.

You can see the workaround we have added in our test suite:
https://github.com/nathanhammond/turborepo/commit/870488735a2d057aba0fe8457d855f3a3e982ede

GitHub Actions runs demonstrating the failure:
https://github.com/vercel/turborepo/runs/8009494656?check_suite_focus=true#step:10:2570
https://github.com/vercel/turborepo/runs/8037161338?check_suite_focus=true#step:10:124

As a reproduction I offer the parent commit of the workaround (fails 100% of the time):
https://github.com/nathanhammond/turborepo/commit/6c6aadacbd5c099cebbd50f0a46d41f6e956febd

Start by running prepare npm@latest --activate in the Windows GitHub Actions reproduction from the parent commit of the workaround, then compare it with the workaround used in the test suite. Trace the first invocation and determine why it times out while subsequent calls succeed; done means the first invocation completes without the workaround.