fix: bump @ioai/wasm-zstd to 1.1.2 and document Next.js integration

[joaner]

Description

Release v1.3.5 on top of release/1.3.4 (no main plot/chart changes).

• Bump @ioai/wasm-zstd from ^1.1.1 to ^1.1.2 and regenerate package-lock.json (resolved from registry.npmjs.org).
• @ioai/wasm-zstd@1.1.2 statically imports the Emscripten glue instead of a runtime import("./wasm-zstd.js"), so inline workers bundled as blob: URLs (e.g. Next.js Turbopack) no longer throw:
  Failed to resolve module specifier './wasm-zstd-*.js'.
• Add Next.js (App Router / Turbopack) integration guidance and a wasm-zstd troubleshooting section in EMBEDDING.md / EMBEDDING.zh.md.

Out of scope for this PR: db3 remote-URL worker changes, architecture/db3 doc updates, and any Plot panel work on main.

Motivation / related issue

• Regression in 1.3.4: @ioai/rosview@1.3.4 + @ioai/wasm-zstd@1.1.1 breaks in Next.js Turbopack (and similar bundlers) when workers run from blob: URLs. 1.3.3 worked because it did not use WASM zstd with a relative dynamic import.
• Release base: main currently includes chart/Plot changes that are not ready to ship; this branch is based on release/1.3.4 so only the wasm-zstd fix and docs ship.
• Downstream: embedders (limx-agent, embodiflow, etc.) need @ioai/rosview@1.3.5 with @ioai/wasm-zstd@1.1.2 for Turbopack/Next.js.

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing behavior to change)
• Documentation update
• Refactor / internal cleanup (no behavior change)

Checklist

• npm run lint passes with no errors
• npm test passes (unit tests)
• npm run build and npm run build:lib succeed
• New behavior is covered by tests (or explain why tests aren't applicable) — No new rosview runtime code; fix is in @ioai/wasm-zstd@1.1.2. Manual verify: Next.js + Turbopack, load zstd-compressed MCAP.
• Documentation updated (README, API.md, EMBEDDING.md) if the public API changed — EMBEDDING.md / EMBEDDING.zh.md updated.
• Breaking change: all affected call sites updated and migration path described in PR description — N/A

API compatibility

No changes to exported symbols in src/entrypoints/index.ts.

• No new, removed, or changed public TypeScript exports.
• Dependency-only: consumers must resolve @ioai/wasm-zstd@^1.1.2 (published separately).
• db3: still requires host-side full download as File for remote use (unchanged from 1.3.4).

N/A

Screenshots / recordings

N/A (dependency + documentation only; no UI changes in this branch).

---

Test plan

1. npm run lint && npm test && npm run build:lib
2. Next.js app with transpilePackages: ['@ioai/rosview'] and client dynamic(..., { ssr: false }) — confirm no wasm-zstd-*.js module resolution error
3. Load a zstd-compressed MCAP via url or local File and confirm playback works