Resolve internal CLI calls with Windows-safe pattern

[evocateur]

To protect Windows from itself, use explicit node path/to/cli.js [..args] call style.

Motivation and Context

The require.resolve() calls were removed in #759, not realizing yarn was going to rain on our parade very shortly. This PR builds on #770, which provides some optimizations to the rimraf calls independent of the local resolution issue.

#708 is fixed by this because we're not letting Windows Script Host get involved at all, instead calling the resolved CLI in the node path/to/cli.js [..args] pattern (which is implicitly what a shebang does, anyway).

How Has This Been Tested?

Local testing, because yet again I am foiled by unstable test snapshots (lerna publish --conventional-commits almost all the way there, except for the timestamps in the changelog output and actual commit history, etc). Le sigh.

Types of changes

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the code style of this project.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[lock]

This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.