Support css modules in storybook

[gyfchong]

Why

Storybook's existing config to process styles is outdated and cannot support both SCSS and CSS modules at the same time.

What

• Created a new storybook config using the latest Vite which supports the functionality out of the box and provides a significant speed boost.

Notes

The DST has had conversations about using next-storybook to remain consistent with the rest of the business however the DS goals require much less config (and support for different config eg. MDX) than the rest of the business, which could lead to slower development time.

Also on the note of config, the next-storybook makes heavy use of custom plugins, due to the complexity it has been difficult to upgrade it to newer versions and config syntax, namely the move to ESM which will take some time to resolve all dependencies which don't support ESM. So if Kaizen were to adopt this technology, we'd potentially lose out on benefits which could improve our productivity.

That isn't to say we shouldn't ever adopt next-storybook just that this isn't the right time to do it as we don't gain very much for the time invested in potentially upgrading it ourselves. Eventually I can see the next-storybook becoming simpler as it no longer needs to cater for things like excluding/including packages for processing styles.

[changeset-bot]

🦋 Changeset detected

Latest commit: 2da5bdd

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages

Name	Type
@kaizen/hosted-assets	Minor
@kaizen/design-tokens	Minor
@kaizen/tailwind	Minor
@kaizen/components	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR