Chore icu 9958 storybook patch babel v7 mode

[calcaide]

🎟️ Jira ticket

Description

• Update @storybook/* to 6.4.x.
• After the updates, we re-audit specific resoltions for @storybook. Resulting in a bunch of them being deleted.
• Missing migrate storybook to babel mode v7, as mentioned in the Jira ticket. We will attempt this later when upgrading other deps because we run into dependency issues when attempted.

How to test this PR:

After every commit, the test procedure it's been building and running @storybook succesfully.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
boundary-ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 29, 2023 10:34pm
boundary-ui-desktop	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 29, 2023 10:34pm
boundary-ui-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 29, 2023 10:34pm

[ZedLi]

This is fantastic!! Thanks for doing this upgrade work!

[ZedLi]

Does this still need to be pinned to patch version, does it work fine now on ^6.4.0? I previously had issues when it was on 6.5.x

Somewhat related, should it actually be 6.5.x for some of these packages in package.json since it looks like some of them are now resolving to 6.5.x anyways as that meets the ^6.4.0 requirements

[calcaide]

@ZedLi

Awesome questions!!

@storybook/addons-docs is getting important changes/deprecations within 6.5, here more information about it. So to minimize noise within this PR I was trying to keep it pined with ~. But definitely planning on deprecation work and upgrade @storybook/addons-doc to 6.5.

---

Absolutely agreed with your second comment.

Upgrading storybook it's hard and easy to get lost within dependencies of dependencies. 
After trying different strategies without much success, pining the main dependencies, such as @storybook/ember, and troublesome dependencies, such as @storybook/docs while being more open with ^ in the rest of them, brings less bugs/noise to validate the entire storybook works after an upgrade. Also facilitates deprecation work.

Then, as you mention, we resolve higher versions than we specify, i.e: we declare @storybook/depA: ^6.4.0 and we resolve @storybook/[email protected]. But re-declaring those, sometimes ends in unexpected bugs/noise and loops of frustration. 

In a nutshell, I am trying to "box" the storybook upgrades efforts in a way that we do baby steps = PR, validate it, and move to the next step (which will be upgrade to ^6.5.x @storybook deps).

Happy to discuss this over slack of zoom 😉

[calcaide]

Closing this PR due to issues when trying to upgrade @storybook. After upgrading it, some magic on the dependencies start making our test that uses sinon.stub to fail.
Spend time debugging and trying to fix it, no luck with it so closing this.