ci: test storybook@next

[merceyz]

What's the problem this PR addresses?

The current latest release of storybook (6.1.18) has an undeclared dependency that we could have caught earlier

cc @gaetanmaisse

How did you fix it?

Test the next version of storybook

Checklist

• I have read the Contributing Guide.
• I have set the packages that need to be released for my changes to be effective.
• I will check that all automated PR checks pass before the PR gets reviewed.

[merceyz]

The stuff failing now was introduced in storybookjs/storybook#13808 cc @shilman

[shilman]

@merceyz sorry about that. @gaetanmaisse and I are on it--thanks for your patience! 🙏

[gaetanmaisse]

I fixed the error currently throwing on master a few days ago (storybookjs/storybook#13916) and thought @shilman cherry-picked it to master but it looks like there was a misunderstanding, so I made a PR to fix master (storybookjs/storybook#13991), I think it will be merged and released in the next 24h.

I don't really know what to think about using next in your E2E as this branch can be quite unstable... I don't want to give you some extra work/failing runs... we have the same E2E test on our side and we clearly neglected it for the last PRs merged on master, it's on us 😞 .

Edit: And this one is to fix next storybookjs/storybook#13992

[merceyz]

I don't really know what to think about using next in your E2E as this branch can be quite unstable... I don't want to give you some extra work/failing runs

That's fine and kind of the point of the e2e test, to catch issues as soon as possible, besides our CI has been red for months so nothing new there. (last time it was green: e448b9e)