fix(reporter): prevent deleting test reports stored in coverage directory

[AriPerkkio]

• Fixes 0.29.7 - 0.31.0 vitest no longer writes to outputFile.junit #3330
• Adds test case for fix: reporter to log version before provider initalizations #3131

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[AriPerkkio]

The Windows CI keeps failing.

This fs.rm fails:

vitest/packages/coverage-c8/src/provider.ts

Line 65 in 9836ccb

await fs.rm(this.options.reportsDirectory, { recursive: true, force: true, maxRetries: 10 })

... when trying to delete this file from previous test run:

vitest/packages/vitest/src/node/reporters/junit.ts

Line 91 in 9836ccb

const fileFd = await fs.open(this.reportFile, 'w+')

// provider.ts
try {
  await fs.rm(this.options.reportsDirectory, { recursive: true, force: true, maxRetries: 10 })
}
catch (e) {
  console.error('Failed to rm reports directory', e)

> Failed to rm reports directory [Error: EPERM: operation not permitted, lstat 'D:\a\vitest\vitest\test\coverage-test\coverage\junit.xml'] {
>   errno: -4048,
>   code: 'EPERM',
>   syscall: 'lstat',
>   path: 'D:\\a\\vitest\\vitest\\test\\coverage-test\\coverage\\junit.xml'
> }

[AriPerkkio]

The Windows CI keeps failing.

Fixed by fix(reporter): close junit file handle. This bug likely only came up in our test/coverage-test setup which is looping the startVitest(). The file handle remained open between test re-runs. I don't think any user ran into this specific error.