feat: add user-specified registry support (from npmrc)

[Kiameow]

🔗 Linked issue

nuxi always using default npm registry #453

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

For user who doesn't have the stable connection to the default npm regsitry, they tend to use the mirror site, but nuxi doesn't have very good support about it (user can set COREPACK_NPM_REGISTRY env to achieve the ideal result, but at least for me, I didn't realize it at first time).

Now the using of nuxi to install a package will directly read the registry info from user's .npmrc file, then change the registry to get package json info as well as the COREPACK_NPM_REGISTRY (if it isn't been set) to download the package

[atinux]

Did you think about using https://www.npmjs.com/package/npm-registry-fetch ?

[pi0]

s.com/package/npm-registry-fetch ?

this looks nice however has lots of ties with Node.js deps and is CJS (also not sure if it respects corepack env, for reasons) I would personally pick simplest approach (can later refactor it out to nypm for easier maintenance)

[danielroe]

I think we can go ahead and merge as a basic implementation and later improve with finer-grained support for per-package registries etc...