Core: Detect no matching export error in storybook start and build

[yannbf]

Closes #23992

What I did

This PR adds a detection step when running storybook dev or storybook build for the infamous No matching exports error (refer to the issue), which is mostly caused by version inconsistencies in Storybook.

Hopefully this will aid users to fix the issues themselves, but ideally this error should give them a command to run, like storybook doctor, which could tell exactly what package to upgrade. For now, we do our best with an error message.

Before:

After:

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!

This is tricky to test, I don't know if it's possible in the monorepo.

1. Create a sandbox
2. Change the version of storybook to something old, e.g. 7.0.3
3. It's crucial that this results in duplicated versions of different Storybook packages, which is why this is tricky in the monorepo given the portaled resolutions which are used.
4. Run Storybook build

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>

[JReinhold]

Haven't tried it out, but the code looks good!