v2 refactor

[northword]

Clear and concise description of the problem

For better sustainability, we are refacting scaffold for the v2 on the dev branch.

We are considering skipping v1 to avoid people thinking that v1 is the stabilized version of v0.

Suggested solution

• use oxc and esrap to parse/print prefs.js Switch to Rolldown? #150 feat!: migrate esbuild+swc to rolldown #161
• use rolldown to bundle test files Switch to Rolldown? #150 feat!: migrate esbuild+swc to rolldown #161
• better way to bundle user input scripts
  • use rolldown to bundle user input scripts Switch to Rolldown? #150 feat!: migrate esbuild+swc to rolldown #161
  • frontend framework support - integration with vite. We chose vite instead of rsbuild simply because I am more familiar with the vite ecosystem, and vite already meets the requirements, with no evident overwhelming advantages of rsbuild.
• redesign the config, moving all build-related confings into config.build, keeping the configuration root level clean
• update the docs
• provide a simple migration script?
• refactor the architecture to make it plugable? low priority
• is there a way to integrate types and toolkit (especially its cli), and perhaps we need a new package (such as ZotEva) to do this? Or it should be placed in v3, and v2 can mainly target integration with vite.

Additional context

No response