fix(reporters): rewrite dot reporter without log-update

[AriPerkkio]

Description

• Fixes issues where log-update hides process.stdout calls that come outside Vitest, e.g. NodeJS deprecation warnings. This is visible for example in Vite repo's test-serve command.
• Fixes issues where log-update got confused of row count and started to duplicate rows
• Improves performance as now we don't render finished tests all the time. There's some logic in DotSummary's onTestFileFinished that optimizes this.
• Removes usage of log-update from dot reporter.

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

Built without sensitive environment variables

Name	Link
🔨 Latest commit	967104c
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/674570ae1717360009119997
😎 Deploy Preview	https://deploy-preview-6943--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 site configuration.

[pkg-pr-new]

@vitest/browser

npm i https://pkg.pr.new/@vitest/browser@6943

@vitest/coverage-istanbul

npm i https://pkg.pr.new/@vitest/coverage-istanbul@6943

@vitest/mocker

npm i https://pkg.pr.new/@vitest/mocker@6943

@vitest/expect

npm i https://pkg.pr.new/@vitest/expect@6943

@vitest/pretty-format

npm i https://pkg.pr.new/@vitest/pretty-format@6943

@vitest/coverage-v8

npm i https://pkg.pr.new/@vitest/coverage-v8@6943

@vitest/runner

npm i https://pkg.pr.new/@vitest/runner@6943

@vitest/snapshot

npm i https://pkg.pr.new/@vitest/snapshot@6943

@vitest/spy

npm i https://pkg.pr.new/@vitest/spy@6943

@vitest/ui

npm i https://pkg.pr.new/@vitest/ui@6943

@vitest/utils

npm i https://pkg.pr.new/@vitest/utils@6943

vite-node

npm i https://pkg.pr.new/vite-node@6943

vitest

npm i https://pkg.pr.new/vitest@6943

@vitest/web-worker

npm i https://pkg.pr.new/@vitest/web-worker@6943

@vitest/ws-client

npm i https://pkg.pr.new/@vitest/ws-client@6943

commit: 1eb3bfb

[sheremet-va]

I just noticed we are still using the old API here... We need to experiment with the new one to see what's missing. Otherwise, it will never be out of the experimental

I don't know if we should do it here, but keep in mind that it needs to be rewritten before 2.2 (I can do it myself, if no one has resources)

[AriPerkkio]

You mean the File part, as in we should use state.getReportedEntity instead?

When building the summary reporter I had at first that one in use and also some new Reporter API hooks. But as nothing was working well I started to reduce amount of changes. First fix all reporter flickering and scrolling issues and then look into new APIs.

[sheremet-va]

Yeah, the File part. Everything else looks nice 👍🏻