CLI: add automigration summary

[yannbf]

Issue: #20222

What I did

Improved the automigration CLI command to provide a summary of what happened.

Successful migrations

No migrations applied

Migration with some success but also failures

Migration with only failures

Migration with multiple failures

In this example, the storybook version specifier is "next", which fails. That's a known bug and we'll fix it in a different PR.

---

Finally, an example with a full output (it's ugly, I know, but we can deal with making the package managers silent later):

How to test

You'll have to build the project, and alias the Storybook CLI binaries to then run in any project of your choosing.

alias sb='$HOME/open-source/storybook/code/lib/cli/bin/index.js'

# in whatever project:
sb upgrade --prerelease

• Is this testable with Jest or Chromatic screenshots?
• Does this need a new example in the kitchen sink apps?
• Does this need an update to the documentation?

If your answer is yes to any of these, please make sure to include it in your PR.

[ndelangen]

@yannbf amazing work!

I was hoping to pair with you on this. I think it's be great if we could pipe the full output (including package manager stdout) into a log file.

[ShaunEvening]

@yannbf amazing work!

I was hoping to pair with you on this. I think it's be great if we could pipe the full output (including package manager stdout) into a log file.

A log file would be lovely :D Especially if it can declutter the CLI output a bit

[ShaunEvening]

Perhaps it's just the specific scenario, but with the errors being the same I would have expected the CLI to bail instead of trying each migration and sharing this.

[ndelangen]

@integrayshaun I think @yannbf likely wanted to demo a bunch of things failing, and made them fail over the same reason.

In normal cases, this these would all fail over different reasons.
Our current strategy is to try to do as many migrations as we can, even if some of them fail.

Changing this would be a pretty big change, at a too late of a stage to change IMHO.

I understand where you're coming from, but getting 1 error at a time, can be just as infuriating and give the user a sensation that the errors will never stop.

By having all the migration ran, and show the errors all in 1 screen, we give the user a sense of how much is broken, and how much they likely need to fix.

If we 'hide' 4 errors, the user doesn't know if we're hiding 4 or 400, and might assume the worse. or assume it's only a single error, and be disappointed when it's "yet another one".

[ShaunEvening]

The fact that we are separating this section with a horizontal line makes me feel like it should sit outside of the summary box... perhaps it's own underneath?

[yannbf]

@yannbf amazing work!

I was hoping to pair with you on this. I think it's be great if we could pipe the full output (including package manager stdout) into a log file.

We could do that! Can you elaborate the use case though? And where the log file would be located?

[yannbf]

The fact that we are separating this section with a horizontal line makes me feel like it should sit outside of the summary box... perhaps it's own underneath?

It could, but the idea was to have a single, final box at the end with the summary. There are a lot of boxes in the output already,it's possible, for instance, to have about 6-7 boxes in a single run if your storybook is quite outdated. The line was just to separate things a little, but we could do something else as well, or even remove the line and add a section in bold, like the "migrations that succeeded" and "migrations that failed" ones

[tmeasday]

This is amazing work @yannbf! We really need Chromatic for our CLI though huh :) (just like we have for the Chromatic CLI ;))