npm installuses non-standard https://registry.npmjs.com invalidating CLI npm login

[cdierkens]

Details

Passing in the flag --auth will forward to an Authorization header which works for retrieving the package details.

However, if you are relying on an npm login session for the final spawnInstall, the authentication is only recognized for the default https://registry.npmjs.org registry

The following change overrode the system default with an explicit default.
v1.10.2...v1.11.0#diff-910193ee18e1d63616f5f4408fca259bR284

I'm proposing an update that matches the default registry with what's on https://docs.npmjs.com/using-npm/registry.html

Expected

Default registry passed into installPeerDeps should match NPM's default registry of https://registry.npmjs.org

Actual

Default registry passed into installPeerDeps is non-standard https://registry.npmjs.com