test: migrate slow tests to use vitest

[erickzhao]

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• The changes are appropriately documented (if applicable).
• The changes have sufficient test coverage (if applicable).
• The testsuite passes successfully on my local machine (if applicable).

This PR moves Electron Forge's slow test suite to use Vitest as a follow-up to #3797. A few notes:

Test migration

Migrating these tests was a lot more straightforward because they run raw commands via child process instead of asserting against mocks. These tests didn't use sinon/proxyquire at all, so I just had to change the Mocha/Chai test harness and assertion calls over to Vitest.

Fixture migration

I moved all files over to /spec/ including test fixtures, so the actual code diff is smaller than it seems.

package.json cleanup

• I also removed all test npm scripts from each individual package's package.json because we run a single instance of vitest from the root of the package rather than using lerna to execute each package's individual scripts.
• chai, mocha, and associated packages are gone!

Removal of unnecessary test utils

I removed expectProjectPathExists and expectProjectPathNotExists from @electron-forge/test-utils since these helper functions were essentially calling fs.existsSync with extra steps.

Workspace organization

The fast and slow suites are now assigned as Vitest workspace projects based on the test file names.

• vitest.config.mts is the base file.
• vitest.workspace.mts contains separate configs for slow and fast tests (mostly just increased test timeouts for the slow test suite).

Note that I had to turn off file parallelism for the time being because there were issues with running multiple test files at once (potentially around FS collisions?). Once this lands, I'll open an issue to track the problem.

[dsanders11]

Another awesome PR! 🎉

I think we could also drop the cross-env dependency in this PR? Looks like it was only used with the Mocha test script commands. Should be able to remove it from package.json and packages/api/core/package.json.

[caoxiemeihao]

[email protected] depends on node18+. However, the Vite template currently uses vite@5 and does not force node to be upgraded to version 18; this may be something that needs to be faced in the near future, because Vite@6 has been released for a while and it also requires node18.
At least I am leaving a message here to attract the attention of forgers.

[erickzhao]

Thanks for the heads-up @caoxiemeihao. We're currently looking at upgrading all Ecosystem projects to Node 22, after which we can finally bump up the supported major version range for Electron Forge!

[erickzhao]

Also as a note: since vitest is only used in CI/testing and we've already only been testing against Node 18, this doesn't block testing/release.

It's definitely a discrepancy, but since we're working on the upgrade anyways, this should be okay.