feat: nodePath & mochaPath

[jjeff]

closes #209

This pull request adds settings for both mochaPath and nodePath. I was hoping this would help me to get electron-mocha working with this extension, but simply swapping out electron-mocha for mocha doesn't seem to do it.

Nonetheless, here's a PR of my changes.

And here's the robot has to say about it:

This pull request introduces new configuration options for specifying the paths to the Mocha and Node.js executables, and updates the code to utilize these configurations. The changes enhance the flexibility of the extension by allowing users to specify custom paths for these executables.

New configuration options:

• README.md: Added descriptions for mocha-vscode.mochaPath and mocha-vscode.nodePath settings, which specify the paths to the Mocha and Node.js executables, respectively.

• package.json: Added mocha-vscode.mochaPath and mocha-vscode.nodePath settings to the configuration schema.

Code updates to use new configurations:

• src/configurationFile.ts: Updated getMochaSpawnArgs method to use the mochaPath setting if defined, falling back to resolving the local Mocha binary path if not.

• src/node.ts: Updated getPathToNode function to use the nodePath setting if defined, logging the path being used.

[Danielku15]

Some remarks on your proposal:

1. Did you find out why your change is not working?
2. We need some unit/integration test for this feature to ensure it is working as expected.
3. I assume these settings should be shared among users via settings.json commited to the repository. This raises some additional concerns about the "path" design:
   • For the alternative package to be used we likely want to assume relative paths. We have to clarify from where they are handled relatively.
   • Node.js is likely installed somewhere on the system and this cannot be properly shared. It would be incorrect to assume a fixed absolute system path.
   • For security reasons it would be likely good to enforce workspace relative paths.

Maybe the following approach could also serve your needs?

Instead of configuring the path to mocha and node we could launch shell/batch scripts with the respective arguments we would pass to mocha. These could be configurable or we simply search for a "mocha.{bat,sh}" in the workspace root if it exists, its used. In this shell script you can then launch any alternative executable and path with the arguments as you like.

[Danielku15]

This change breaks proper caching of the variable and cause re-evaluation on every spawn of mocha. We should keep the caching for the locally resolved path as it can be expensive in some scenarios.

[Danielku15]

Your issue only talks about redirecting Mocha to anoter tooling. What's the real usecase behind redirecting node as well? Depending on your need also NPM would need support for reconfiguration.