Add msw and Vitest globalSetup default/conventional paths to coverage exclude defaults

[astorije]

Clear and concise description of the problem

It is not uncommon to use msw and Vitest/Jest together (for good reasons, Vitest and msw are both ❤️). Would you be open to excluding **/mockServiceWorker.js from the default coverage files?

Same question about: globalSetup: "./vitest.globalSetup.ts", would **/vitest.globalSetup.(c|m)[jt]s be a good default to include?

Suggested solution

I am happy to open a PR / PRs to add those if you think this is a reasonable addition.

Alternative

A the moment, we are excluding these with:

exclude: [
  ...coverageConfigDefaults.exclude,
  "public/mockServiceWorker.js",
  "vitest.globalSetup.ts",
],

which of course is absolutely fine, but I wanted to check with y'all if this is something that would be beneficial to the community :)

Additional context

No response

Validations

• [X] Follow our Code of Conduct
• [X] Read the Contributing Guidelines.
• [X] Read the docs.
• [X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.