[rush-lib] Update [dot]npmrc

[L-Qun]

Since https://registry.npmjs.org/ is already the default npm registry, there's no need to configure it explicitly. Otherwise, it will override the user's local configuration

[iclanton]

The repo maintainer generally wants to control which registry the repo talks to explicitly, so overriding whatever the user has configured is the desired behavior. For example, this repo explicitly uses the public registry because it's an OSS project. If a developer has a private registry configured that does not have the public registry configured as an upstream and runs rush install, their installation is likely to fail.

[L-Qun]

@iclanton The public npm registry (https://registry.npmjs.org/) is the default registry for all standard npm and pnpm setups. Unless a developer has explicitly changed it, it will be used automatically. Hardcoding it provides no additional benefit.

[iclanton]

The additional benefit is the repo owner ensuring that an individual user's override isn't used.

[L-Qun]

@iclanton But doesn't it introduce even bigger problems? Users typically won’t notice this configuration after generation, but they’ll have to spend time later figuring out why things are failing. Usually, every company has its own registry, which means as long as they run this command, they’re guaranteed to run into issues.