fix: rerun tests, when setup file is edited

[mysteryven]

fix: #2614

1. I used tests similar with test/related. Maybe it's not explicit, but it can tell me setup files have been added into forceRerunTriggers. I will be really happy to know whether there are some better way to test it.

2. Do I need to modify the document of forceRerunTriggers's default values ?

-['**/package.json/**', '**/vitest.config.*/**', '**/vite.config.*/**']
+['**/package.json/**', '**/vitest.config.*/**', '**/vite.config.*/**', '/path/to/setupFiles']

[sheremet-va]

Thank you for your PR! Please, remove pnpm-lock file and add a note to docs that changing setup file will trigger rerun of all user tests.

[mysteryven]

Thank you for your PR! Please, remove pnpm-lock file and add a note to docs that changing setup file will trigger rerun of all user tests.

Done, but the CI failed due to the outdated lock-file.

[Maxim-Mazurok]

I can confirm it's working in 0.27.2, thank you!

For what it's worth, I've switched from manually defining restHandlers for MSW in setup file to using msw-snapshot package from NPM, which allows to basically cache actual API responses as snapshots, and then use them in tests. I think it's a much nicer approach, allowing for an easy and good contract.