chore: fix wasm release and benchmark grouping

[raphaelmansuy]

Summary

• disable WASM npm publication while still building and attaching the packaged tarball to the GitHub release
• split benchmark grouping to separate non-ocr and hybrid, and add the edgeparse benchmark config needed to preserve metrics while optimizing speed
• update the Astro site/docs to use the shared benchmark snapshot and document the new grouped benchmark runs

Validation

• cargo test -p edgeparse-core -p edgeparse-cli
• cargo clippy -- -D warnings
• cargo fmt --all --check
• cargo check -p edgeparse-wasm --target wasm32-unknown-unknown
• python3 -m py_compile benchmark/compare_all.py benchmark/src/engine_registry.py benchmark/src/pdf_parser_opendataloader_hybrid_docling_fast.py benchmark/src/pdf_parser_opendataloader_hybrid_hancom.py
• cd sdks/python && maturin build --release --out dist/ && pytest tests/ -v
• cd sdks/node && npm ci && cargo build --manifest-path ../../crates/edgeparse-node/Cargo.toml --release && npm run build:ts && npm test
• cd demo && npm ci && DEMO_BASE_PATH=/demo/ npx vite build
• cd site && pnpm install --frozen-lockfile && pnpm run build
• cargo audit --ignore RUSTSEC-2025-0020
• cargo deny check

Notes

• local Docker validation was not possible here because the Docker daemon is unavailable in this environment; the PR CI job should validate the smoke build on GitHub runners