React: Implement manifests/component.json for React

[kasperpeulen]

closes #32705, closes #32706, closes #32670, closes #32671, closes #32672, closes #32703, closes #32669,

What I did

• Manifest - Build essential generation flow for production builds #32705
• Manifest - Extract example snippets #32706
• Manifest - Extract descriptions #32670
• Manifest - Extract component description from component JSDoc #32671
• Manifest - Extract component description from meta JSDoc #32672
• Manifest - Extract all JSDoc tags #32703
• Manifest - Support generation in dev server #32698
• Manifest - Extract prop types #32669

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

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

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-storybook/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 publish.yml --field pr=<PR_NUMBER>

Summary by CodeRabbit

• New Features

  • Experimental component manifest generation (writes JSON during static builds) and an HTTP endpoint to serve component manifests; renderer exposes an experimental manifest generator.

• Updates

  • Improved CSF/story parsing and play-function handling; richer JSDoc/react-docgen metadata extraction and utilities; added code-snippet generation for story examples; small dependency updates.

• Tests

  • Extensive tests covering snippet generation, manifest generation, JSDoc parsing, and docgen matching.