Fix #686
Fix #682

Instead of deleting the whole `target/` directory, leave it alone so the symlink
driving the `npm link`/`yarn link` stays in tact.

Leave Vite builds in their build directories (`/lib-build`/`/asset-build`)
so you can `vite build --watch` to build on local changes and still have a
consisent place to reference in the `package.json` `exports`. Previously,
everything relied on `build.sh` which does a bunch of moving and renaming
and made it hard to rebuild on changes.

Add back support for CommonJS (adding the `package.json` `exports`).

The last piece is making sure the `?url` imports (`import workerPath from 'hydrogen-view-sdk/main.js?url';`)
work still. It looks like this may have just been solved via
vitejs/vite#6725 -> vitejs/vite#7073
(literally 2 days ago) and we just need to wait for the next Vite release 🎉

…opment-and-commonjs

Conflicts:
	package.json
	scripts/sdk/base-manifest.json

Update to Vite which includes vitejs/vite#7098

…opment-and-commonjs

Conflicts:
	package.json
	scripts/sdk/base-manifest.json
	scripts/sdk/build.sh

See #693 (comment)

…opment-and-commonjs

Conflicts:
	scripts/sdk/build.sh

See #693 (comment)

Fix #722

Updating Vite to includes fixes from
vitejs/vite#7822 -> vitejs/vite#7827

…opment-and-commonjs

…opment-and-commonjs

Conflicts:
	scripts/sdk/base-manifest.json

…opment-and-commonjs