TISTUD-5419 Improve detection of existing Node.js installs using registry on Windows
TISTUD-5419 Improve detection of existing Node.js installs using registry on Windows
  - Verify that path registry points to exists, otherwise move on to searching PATH
Merge branch 'TISTUD-5419' of github.com:sgtcoolguy/studio3 into TISTUD-5419

Conflicts:
	plugins/com.aptana.js.core/src/com/aptana/js/internal/core/node/NodeJSService.java
TISTUD-5426 Avoid modifying the permissions on the tizen downloadable temp directory
  - Move my performance hack down from TitaniumSDKTools.extract. When we can (non-Windows, no modifying content as we extract, no prompting on conflicts) - use the native unzip binary to unzip. This should be quicker since it _should_ retain permissions and we don't need to extract files using Java ZipEntry API and then run chmod on all of them!
TISTUD-5431 Node Package Installer: application npm install location is incorrect
Merge pull request #118 from sgtcoolguy/TISTUD-5419

TISTUD-5419 Improve detection of existing Node.js installs using registry on Windows
Merge pull request #119 from pinnamur/TISTUD-5431

TISTUD-5431 Node Package Installer: application npm install location is incorrect
TISTUD-5417 Inconsistent PATH lookup for Node and other components
  - Refactor so INodePackageManager is tied to an INodeJS installation and we explicitly execute npm commands underneath that node install
  - Break out an INodeJS interface and impl to represent a NodeJS install, ove some functionality from INodeJSService there.
  - Renamed some INodeJSService methods to make more explicit what they return.
  - Update callers to use new API
Merge pull request #120 from sgtcoolguy/TISTUD-5417

TISTUD-5417 Inconsistent PATH lookup for Node and other components