Dev Kit Can't Recognize NPM which installed by fnm

[ZYUN-MSFT]

Describe the bug

Dev Kit Can't Recognize the NPM command which is installed by fnm.

Details

On a totally new environment and install node.js with fnm:

Check pre-requirements failed and create new add-in failed:

I guess this may related to the special method that fnm make the system link, or the special way VSCode read environment vars.

Notice

fnm is an Node.js official recommend way to install node.js (from Node.js official website):

[ZYUN-MSFT]

Update some investigation:

1. fnm MUST have to initialize the env var by fnm command, otherwise the node npm can't be found
2. Initial script in Pwsh's profile don't affect Windows default new process
3. Due to this design, fnm can live together with official system installed node.js, that means on no fnm command init profile's shell, the system default node.js will be used.
4. Due to 3., this issue can be work around by manually install a system level official node.js (Already verified)

Due to above, I suggest not to fix this issue for now, since we can't cover every node.js version manager's every special behaviors.