test: migrate Vitest tests to Rstest

[9aoy]

Summary

migrate vitest tests to rstest

• migrate vitest tests to rstest
• use rstest projects instead of legacy vitestRunAll
• use path-serializer instead of createSnapshotSerializer helper in @scripts/vitest-config https://www.npmjs.com/package/path-serializer
• use Unit Test (macOS/Windows) workflow instead of Unit Test (vitest - macOS/Windows) workflow, and we will migrate jest tests to rstest later

before:

the main reason is that the vitest version and testing methods in modern.js are outdated.

after:

Related Links

https://rstest.rs/guide/migration/vitest

Checklist

• I have added changeset via pnpm run change.
• I have updated the documentation.
• I have added tests to cover my changes.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c76c3a7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Rsdoctor Bundle Diff Analysis

📁 bundle-diff

Path: benchmark/bundle-diff/dist/rsdoctor-data.json

📌 Baseline Commit: 8a30828c2e | PR: #7922

Metric	Current	Baseline	Change
📊 Total Size	497.5 KB	497.5 KB	0 B (0.0%)
📄 JavaScript	487.6 KB	487.6 KB	0 B (0.0%)
🎨 CSS	1.2 KB	1.2 KB	0 B (0.0%)
🌐 HTML	5.9 KB	5.9 KB	0 B (0.0%)
📁 Other Assets	2.8 KB	2.8 KB	0 B (0.0%)

📦 Download Diff Report: bundle-diff Bundle Diff

Generated by Rsdoctor GitHub Action