chore(reporter): fix deprecation message and add to docs

[nozomuikuta]

Description

No related issues.
Resolves a Discord message

The basic reporter will be removed in Vitest 4.
But, its deprecation is not explained in docs.

I also changed the version in warning message in console, but I can revert this part because it would be just a plan at that moment and so that you can avoid a new release for v3. Please let me know how you want me to do.

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.
• Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

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 vitest-dev ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	8fe529f
🔍 Latest deploy log	https://app.netlify.com/projects/vitest-dev/deploys/68f2acac53dd690008690233
😎 Deploy Preview	https://deploy-preview-8734--vitest-dev.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 project configuration.

[nozomuikuta]

Not sure, but is it expected for some CI to fail?
I mean, other PR also fails due to similar CIs.

[AriPerkkio]

We don't really mention breaking changes in the option configuration themselves. These are mentioned in migration guide.

[nozomuikuta]

@AriPerkkio

Thank you for telling me the information architecture of documentation!
Then, should I close this PR or just keep the changes on console warning?

[AriPerkkio]

Let's close this. The warning was removed in

• fix!: remove 'basic' reporter #7884