CLI: Warn the user for duplicated versions after automigrate

[yannbf]

Closes #

What I did

When users migrate projects, they might end up having issues in Storybook due to duplicated versions of dependencies, which might clash in the major range. They could come as direct but also transitive dependencies. This PR adds a feature to the CLI's automigrate command to warn users when such scenario happens.

Here's an example when there are duplicated versions for conflicting packages in a pnpm project:

Here's an example when there are also duplicated major versions in a yarn2 project:

How to test

1. Create a sandbox for template, e.g. yarn task --task sandbox --start-from auto --template react-vite/default-ts
2. Install conflicting versions e.g. (yarn add @storybook/addon-actions@6.0.0)
3. Run code/lib/cli/bin/index.js automigrate in that sandbox
4. See the warning

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

[tmeasday]

This is great! Is it possible to run the check without automigrating? As a like sb doctor type command? Or would you just suggest folks run yarn sb migrate?

[tmeasday]

Great!