CLI: Split sb-scripts into two different migrations

[yannbf]

Issue: N/A

What I did

This PR changes the sb-scripts migration into two migrations:

• One that takes care of sb binaries
• Another that takes care of sb scripts

This way each migration is more focused, and they can happen independently of each other

Additionally, the sb binaries migration will make sure that sb is removed and users always use storybook instead. The usage of sb in scripts is also updated to storybook.

Use cases

sb-binary: User does not have storybook - it's installed

sb-binary: User has storybook lib but also sb - sb is removed

sb-binary: User does not have storybook and does have sb - storybook is installed and sb is removed

sb-scripts: Scripts are updated and sb becomes storybook

How to test

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

[shilman]

@yannbf in your last image, what is storybook build build? that looks like a bug?

[yannbf]

@yannbf in your last image, what is storybook build build? that looks like a bug?

No, I just noticed that the repo I used to test this had "build-storybook": "storybook-build build". Problem is on my end! The tests are correct and would have picked that issue

[kasperpeulen]

Looks great, thanks @yannbf