ui: load bundle split vendor and code

[nopcoder]

• Update @duckdb/duckdb-wasm to v1.28.0
• Vite build using chunks - split vendor code

Close #7134

[arielshaqed]

This looks generally cool. I have some questions though about the issue, based on this:

❯ du -sh dist/assets/*
268K    dist/assets/duckdb-browser-eh.worker-80bdeff3.js
320K    dist/assets/duckdb-browser-mvp.worker-91331f4b.js
17M     dist/assets/duckdb-eh-13ec0755.wasm
21M     dist/assets/duckdb-mvp-a4aa3c03.wasm
324K    dist/assets/index-0308a6b6.css
6.5M    dist/assets/index-90011776.js

• Optimize cache usage. Code changes is much more common than package changes.

Not sure that this is true, but in any case neither is that common. We're saving, what, one <6MiB download per update? When DuckDB is 17MiB + 21MiB?

• Parallel downloading. Download the vendor code and other chunks simultaneously.

Again, there is little to gain here given DuckDB.

We should measure and see how this changes things. So approving because this doesn't harm us, but not sure it how it helps our users.

[nopcoder]

DuckDB wasm is dynamically loaded. Downloaded only when you open the duckdb shell.

Parallel load - this is how it looks like after the change:

If we will switch to dynamic load for the file viewers - render notebook for example we can split the vendor package and load only partial code.

The only benefit is the cache reuse - assume you change your code and not react.