feat(vitest): add --disable-console-intercept option to allow opting-out from automatic console log interception

[hi-ogawa]

Description

Closes #1405

I'm not sure --spy-console-log is a good way to name this option. It might be better to negate the logic so that this option can be named as --keep-raw-console or something. I would appreciate if someone could help me with better wording and also what to put in doc/jsdoc.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for fastidious-cascaron-4ded94 ready!

Name	Link
🔨 Latest commit	256d65d
🔍 Latest deploy log	https://app.netlify.com/sites/fastidious-cascaron-4ded94/deploys/658e94f5aadc4a000829e933
😎 Deploy Preview	https://deploy-preview-4786--fastidious-cascaron-4ded94.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sheremet-va]

I don't like the naming to be honest. Vitest doesn't "spy" on the console, it intercepts it. Maybe --disable-console-intercept?

[hi-ogawa]

Thanks for the suggestion. I like --disable-console-intercept better as well. I think it also helps wording better in the doc.