增加 nrm（NPM registry manager）镜像源管理功能

[jackhb1999]

Description

既然 vp 已经把 nvm 的功能做了，nrm 的也加上吧。

Suggested solution

Commands:
vp nrm ls List all the registries
vp nrm current [options] Show current registry name or URL
vp nrm use [name] Change current registry
vp nrm add [home] Add custom registry
vp nrm login [options] [base64] Set authorize information for a custom registry with a base64 encoded string or username and password
vp nrm set-hosted-repo Set hosted npm repository for a custom registry to publish package
vp nrm set-scope Associating a scope with a registry
vp nrm del-scope Remove a scope
vp nrm set [options] Set a custom registry attribute
vp nrm rename Change custom registry name
vp nrm del [name] Delete custom registry
vp nrm home [browser] Open the homepage of registry with optional browser
vp nrm test [registry] Show response time for specific or all registries
vp nrm help [command] display help for command

Alternative

No response

Additional context

No response

Validations

• Read the Contributing Guidelines.
• Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
• Check that there isn't already an issue requesting the same feature.

[naokihaba]

@jackhb1999 cc @fengmk2

Thanks for the suggestion. Could you help us understand the specific problems you run into when you use nrm or npm config set registry with Vite+?

We would love to know more about the workflows where you feel registry management needs to be part of the tool itself. Is the main goal to make things more convenient, to ensure compatibility with managed runtimes, or perhaps to keep things consistent across different platforms?

It would also be helpful to know if you would need every single nrm command, or if a smaller set of features would be enough for what you have in mind.

If you have any concrete examples, please feel free to share. It will help us decide if this fits within Vite+ and how we should approach the implementation.