fix(core): npmrc should be obeyed during nx migrate

[AgentEnder]

Current Behavior

Calling nx migrate 'my-package' does not obey registry settings from .npmrc. This leads to things like trying to pull latest from npm, or yarn registry instead of the registry pointed to by the workspace.

If an enterprise workspace was using a private registry, and had a custom nx plugin, they would not be able to use nx migrate for their internal migration scripts.

Expected Behavior

Registries and authorization headers in .npmrc should be obeyed by nx migrate

Workaround

Setting environment config variables does work, such as export NPM_CONFIG_REGISTRY=...., but these cannot be scoped to certain scopes etc.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nrwl/nx-dev/J7kaxD1n71FsDCXN1hR4uS34Sjzg
✅ Preview: Canceled

[Deployment for a4e2faf canceled]

[nx-cloud]

Nx Cloud Report

CI ran the following commands for commit a4e2faf. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status	Command
	nx affected --target=e2e --base=44db568261e93e252d1a89af262c6532e0ce1215
	nx affected --target=lint --base=44db568261e93e252d1a89af262c6532e0ce1215 --parallel --max-parallel=4
	nx affected --target=test --base=44db568261e93e252d1a89af262c6532e0ce1215 --parallel --max-parallel=2
	nx affected --target=build --base=44db568261e93e252d1a89af262c6532e0ce1215 --parallel --max-parallel=3
	nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[FrozenPandaz]

Some minor requests

[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.