browser: fix peer dependency issue

[gabrocheleau]

This PR fixes this peer dependency issue that appeared when running npm run install-browser-deps

> npm install webdriverio @vitest/browser web-streams-polyfill

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: root@undefined
npm ERR! Found: vitest@1.5.0
npm ERR! node_modules/vitest
npm ERR!   peer vitest@"1.5.0" from @vitest/coverage-v8@1.5.0
npm ERR!   node_modules/@vitest/coverage-v8
npm ERR!     dev @vitest/coverage-v8@"^1.2.2" from the root project
npm ERR!   peer vitest@"1.5.0" from @vitest/ui@1.5.0
npm ERR!   node_modules/@vitest/ui
npm ERR!     peerOptional @vitest/ui@"1.5.0" from vitest@1.5.0
npm ERR!     dev @vitest/ui@"^1.2.2" from the root project
npm ERR!   1 more (the root project)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @vitest/browser@"^1.5.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: vitest@1.5.2
npm ERR! node_modules/vitest
npm ERR!   peer vitest@"1.5.2" from @vitest/browser@1.5.2
npm ERR!   node_modules/@vitest/browser
npm ERR!     peerOptional @vitest/browser@"^1.5.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

[acolytec3]

Sadly, we still have this "failed to fetch dynamically imported module" thing. I saw this when I was trying to fix via #3369. I think there is still an obscure browser related testing bug in vitest.

[gabrocheleau]

Sadly, we still have this "failed to fetch dynamically imported module" thing. I saw this when I was trying to fix via #3369. I think there is still an obscure browser related testing bug in vitest.

Ah! missed that other PR. Will close this on in favor of #3369