Update configurations for node plugin to use a single version of binaries; remove yarn configurations

[labkey-susanh]

Rationale

Our default configuration for modules using npm is to have each module act independently, using its own downloaded version of node and npm. We have a good number of modules using npm, so this leads to our having lots of redundant copies of these binaries in play while developing. We recently removed support for standalone module building, so there is no real compelling case for the current default configuration. We've also recently seen builds failing when trying to download the binaries for some of the modules that are built later in the build process. Though we don't know that it is because of our downloading the binaries multiple times, we also don't know that that isn't the cause.

This PR changes our default configuration for the npmSetup task to have only the :server project do the downloading, stashing the binaries under the .node directory. Other modules are configured with this download directory as their work directory for both node and npm. If any modules need to be differently configured (with a different version of node or a different working directory), they can still do so by setting up their own configuration of the npm extension.

We also remove the configurations related to yarn tasks since we do not anticipate having any projects using yarn.

Related Pull Requests

Changes

• Update default configuration for npm plugin
• Remove configuration code related to yarn.
• Update from nodeModulesDir to nodeProjectDir for latest version of node plugin.