fix: switch buttplug WASM to --target web for browser compatibility

--target bundler generates static WASM ESM imports that only work
through a bundler (vite-plugin-wasm). --target web generates fetch-based
WASM loading via import.meta.url which browsers handle natively.

- Change wasm-pack build target from bundler to web
- Call wasmModule.default() (init) after import in maybeLoadWasm
- Restore rollupOptions.external so WASM stays a separate fetch
- Removes the need for vite-plugin-wasm in any consumer

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

packages/buttplug/package.json

@@ -10,7 +10,7 @@
   ],
   "scripts": {
     "build": "vite build",
-    "build:wasm": "wasm-pack build --out-dir wasm --out-name index --target bundler --release",
+    "build:wasm": "wasm-pack build --out-dir wasm --out-name index --target web --release",
     "serve": "node serve.mjs"
   },
   "dependencies": {