fix: Add better version detection

[ngirardin]

This is a follow-up PR for #118 which have broken some installs:

• Vitest not starting up due to failed version check on windows #88 (comment)

It seems to fix:

• Vitest version not detected #124
• Vitest version not detected #124
• Vitest plugin executes non test files #90
• Not able to get version on MacOS (0.2.37) #131

and probably:

• Use closest vitest.config.ts from the test file for mono repo #13

In some cases, vitest need to be started using spawn(vitestCommand.cmd, [...vitestCommand.args, '-v'], envs)), and in other by using spawn(process.execPath, [vitestCommand.cmd, ...vitestCommand.args, '-v'], envs)).

There are lot of OS / Node install combinations, and I don't have a clear picture of which to use and when.

The easiest fix that I could find, was to try both commands and see which one worked.

It's not the cleanest solution, but I'm open to suggestions :)

[ngirardin]

@zxch3n any thoughts on the fix? (I can't add you as a reviewer)

[zxch3n]

This fix should use try and catch to avoid throwing in each step, right?

[arimgibson]

Hey @ngirardin , let me know if you need help making those suggestions from @zxch3n ; happy to help move this forward if there's anything I can do!

[ngirardin]

Thanks @zxch3n for the review.

I've made some changes to the code:

• log the commands that are spawned
• added a message to invite users to open an issue and provide their logs if no version is detected
• trying both of the spawn methods for starting npx (when command == null)
• added some tests (WIP needs to mock spawn to test all the cases)
• added a check when doing the line.match to avoid crashing if the version is not found in the output

@arimgibson, sorry for the delay, please let me know if you see something to change on this code :)