fix: handle spaces in node bin path

[cristiand391]

Reported here:
forcedotcom/cli#2564

plugin-plugins v4 will always perform a check to ensure a plugin exists in npm (npm show <plugin> dist-tags), since it uses the bundled npm instead of the global one it requires to call it using node (so it tries to get the path to node and path to npm-cli.js).

on plugin-plugins v3 this check would only happen if you tried to install a plugin and:

1. its name didn't include a @
2. root CLI didn't specify `pjson.oclif.scope

but await this.npmHasPackage(unfriendly) was always silently failing on windows (prob on mac/linux too) if the path to node contains spaces.

plugin-plugins/src/plugins.ts

Line 93 in 5ba86b5

if (unfriendly && (await this.npmHasPackage(unfriendly))) {

v4 made npmHasPackage thrown on not found:

plugin-plugins/src/plugins.ts

Lines 125 to 126 in 76ea070

	// validate that the package name exists in the npm registry before installing
	await this.npmHasPackage(name, true)

This PR fixes the error caused on windows when the path to the node binary contains spaces.