fix(vitest): fix tap reporter to handle custom error

[hi-ogawa]

Description

• Closes Vitest internal unhandled error when test throws custom error without { name: string } with tap reporter #4885

Currently processError (from @vitest/utils) returns any, but it looks like most of the usages expect it to be ErrorWithDiff. ErrorWithDiff requires name: string, but processError doesn't seem to guarantee this when odd things are thrown.

Fixing processError might be better in a long run, but for this PR, I just adjusted tap reporter to do something similar as other reporters in printErrorMessage:

vitest/packages/vitest/src/node/error.ts

Lines 208 to 209 in 67e3211

	function printErrorMessage(error: ErrorWithDiff, logger: Logger) {
	const errorName = error.name || error.nameStr || 'Unknown Error'

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 canceled.

Name	Link
🔨 Latest commit	78e1749
🔍 Latest deploy log	https://app.netlify.com/sites/fastidious-cascaron-4ded94/deploys/659b4fd9da52eb00080c8f6a