Build: Re-enable Storybook in Vite Ecosystem CI

[shilman]

Describe the bug

Once upon a time, Storybook was part of https://github.com/vitejs/vite-ecosystem-ci. At some point it broke, and was removed. Now every time Vite makes a change, maintainers don't know whether they've broken Storybook.

There is a draft PR to re-enable it: vitejs/vite-ecosystem-ci#137. We should pick that up and take it over the line, or start again if that's easier.

Update 30 July 2024

The initial PR got superseded by vitejs/vite-ecosystem-ci#311 where we provided scripts for the vite-ecosystem CI inside of our monorepository. The problem is that our scripts depend on esbuild-register, which currently has a bug preventing us from continuing our second attempt at integrating Storybook into the Vite Ecosystem CI.

To circumvent the esbuild-register solution, we planned to continue @ndelangen work to move away from esbuild-register and to use bun instead, which is already used for some tasks. This PR tries to do the migration.

Even after multiple attempts, we could not migrate fully to Bun at the moment. Bun has some different behaviors from Node.js. For example, we had huge issues to make `

Third attempt

Instead of trying to integrate Storybook into Vite's Ecosystem CI via our sandboxes repo (first attempt) or by integrating Storybook by using our mono repository (second attempt), we want to initialize a fresh repository exclusively for Vite's Ecosystem CI. We want to modify our daily sandbox publishing script to release a react-vite sandbox into a separate repository. The package.json of this repo will provide scripts for Vite's ecosystem CI to install dependencies and to run the test-runner to execute tests.

The scripts we will provide will be the following:

• vite-ecosystem-ci:test: Running the @storybook/test-runner