Improve `npm install -g` and Node.js version management

Reference: https://github.com/voidzero-dev/vite-plus/pull/1974#issuecomment-4831760534, https://github.com/voidzero-dev/vite-plus/pull/1974#issuecomment-4831792749

Vite+ injects a prompt when `npm install -g` finishes and create shims to make bins accessible when the npm prefix is not in `$PATH`. This logic sometimes causes tricky bugs (https://github.com/voidzero-dev/vite-plus/pull/1974#issue-4762339551), and there is some overlap with vp install -g responsibilities.

According to https://github.com/voidzero-dev/vite-plus/issues/528, https://github.com/voidzero-dev/vite-plus/issues/540, `npm install -g` is used to satisfy users who want to install packages in one certain Node.js's bin directory. And the bin should be usable only when using this Node version.

I believe the there is a room to improve the interaction logic here.

Start by comparing the `npm install -g` and `vp install -g` interaction described here with the discussions in issues 528 and 540 and the referenced pull request comments. The work is done when the installation behavior, Node.js-version-specific bin availability, prompt handling, and shim responsibilities are clearly defined without the reported bugs or overlap.

Written by the indexing model from the issue text.