chore: use tinyglobby instead of fast-glob in Vitest

[benmccann]

This reverts commit 70baaaa.

Description

Discussed here: #6688 (comment)

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	5df1978
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/67b2886709208c0008bcc668
😎 Deploy Preview	https://deploy-preview-7504--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.

[AriPerkkio]

Was it Storybook whose tests failed after this change previously, @sheremet-va? They are not in the ecosystem-ci so we'll need preview release for them to try.

[pkg-pr-new]

@vitest/browser

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

@vitest/coverage-istanbul

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

@vitest/expect

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

@vitest/pretty-format

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

@vitest/mocker

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

@vitest/coverage-v8

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

@vitest/runner

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

@vitest/snapshot

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

@vitest/spy

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

@vitest/ui

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

@vitest/utils

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

vite-node

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

vitest

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

@vitest/web-worker

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

@vitest/ws-client

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

commit: 5df1978

[AriPerkkio]

cc. @JReinhold

[JReinhold]

Looks good in Storybook, everything works!

To be safe, I also tested with Vitest 2.1.0 (the original tinyglobby migration) and that was still broken, 2.1.3 (the revert) worked as expected, and so did this PR version.

For full context, in Storybook's CI we have a lot of stories/tests symlinked into ecosystem directories, and they wouldn't get picked up by the faulty versions of Vitest, but they are with this version.