Prefer project scoped node/npm binaries over global binaries

[mshima]

Closes #14249

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• jhipster-online was updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (bellow reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[atomfrede]

This looks good. Should we merge it?

[DanielFran]

@mshima is it OK to merge?

[mshima]

IMO yes.

Worth noting:

• Gradle will match maven behavior and use a local version of node/npm.
  It will fail at apple silicon due to Support for Apple Silicons architecture aarch64/arm64 node-gradle/gradle-node-plugin#154.
  Sadly the user will have to disable npmInstall or update to node 16.
• I couldn't implement .npmw wrapper for gradle because gradle plugin creates a versioned path to npm binary.

cc @atomfrede

[atomfrede]

Good to know. Nevertheless let's merge it.

[mshima]

The failures seems related to npm/cli#2715.

[atomfrede]

So related to #14934. Should we add --no-audit to maven/gradle execution until its fixed upstream?