Portable stories: Introduce experimental Playwright CT API and Support for more renderers

[yannbf]

Closes #26026

What I did

This PR is a collection of many different satellite PRs that got worked on and reviewed by both @yannbf and @JReinhold, introducing the following work:

• Experimental Playwright CT API for React
• Experimental Playwright CT API for Vue3
• Portable stories support for Next.js (Jest)
• Portable stories support for Svelte (Vitest)
• Distribute CJS entry points for preview entries of addons
• API docs for portable stories
• Recipes for using portable stories in Jest, Vitest and Playwright CT (for applicable renderers)

A lot of the file changes are actually the introduction of a "portable-stories-kitchen-sink" test storybook directory, which includes all the necessary files for testing the different integrations locally and in CI.

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

1. Run a sandbox for template, e.g. yarn task --task sandbox --start-from auto --template react-vite/default-ts
2. Follow instructions for portable stories in Jest, Vitest or Playwright CT
   

Documentation

• 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>

[yannbf]

@SocketSecurity ignore-all