Merge bento-design-system and storybook packages

[gabro]

This PR brings Storybook back into bento-design-system.

We currently use storybook as a separate package as a sort of smoke test for using @buildo/bento-design-system from a client perspective.

However, this has the major drawback of having an unconventional storybook setup which has these disadvantages:

• tools like TurboSnap won't work (this is the main motivation for this PR, as it's costing us potentially thousands of euros a year in redundant snapshots)
• we hit bugs like https://github.com/buildo/bento-design-system/blob/main/packages/storybook/stories/index.tsx#L14-L28, which cause some friction in our setup
• the setup for working locally is a bit tricky (we need to configure turborepo to wait on a successful bento build before running the storybook)
• iterating on a storybook is slower because it requires rebuilding the whole library before seeing a change in the storybook, and this takes ~10-20s on my machine.

For this reason, I think as of now the cons are much bigger than the pros, and we still achieve some of the props via some other smoke testing and/or tools like https://github.com/arethetypeswrong/arethetypeswrong.github.io

[gabro]

Future improvements once this is merged:

• enable TurboSnap (Enable TurboSnap in Chromatic #659)
• enable https://github.com/arethetypeswrong/arethetypeswrong.github.io/
• remove the deprecated createBentoComponents in the next breaking release
• (potentially) migrate Storybook from Webpack to Vite (making sure https://github.com/IanVS/vite-plugin-turbosnap works first)

[veej]

Just a small doubt, but LGTM 👍

[veej]

Also, there's a story that is generating flaky chromatic diffs :(