fix: move workspace name prop to test (#1)

What I did

name prop in vitest workspaces should be in test object instead of root. Otherwise we get a typescript error.

Checklist for Contributors

Documentation

[x] Add or update documentation reflecting your changes
[ ] If you are deprecating/removing a feature, make sure to update MIGRATION.MD

Checklist for Maintainers

[ ] When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts
[ ] Make sure this PR contains one of the labels below:

Available labels
- `bug`: Internal changes that fixes incorrect behavior. - `maintenance`: User-facing maintenance tasks. - `dependencies`: Upgrading (sometimes downgrading) dependencies. - `build`: Internal-facing build tooling & test updates. Will not show up in release changelog. - `cleanup`: Minor cleanup style change. Will not show up in release changelog. - `documentation`: Documentation **only** changes. Will not show up in release changelog. - `feature request`: Introducing a new feature. - `BREAKING CHANGE`: Changes that break compatibility in some way with current major version. - `other`: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

_core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>_

Greptile Summary

This pull request addresses a TypeScript error in the Vitest workspace configuration documentation for React.

Moved 'name' property from root level to 'test' object in React configuration example in docs/_snippets/vitest-plugin-vitest-workspace.md
Corrects the structure for Vitest workspace configurations, resolving a TypeScript error
Only affects the React configuration example; Vue and Svelte configurations remain unchanged
Documentation has been updated to reflect this change, as indicated in the PR checklist

storybookjs / storybook