Upgrade Docxodus service and renderer to 12.4.1

[JSv4]

Upgrade DOCX ingestion and rendering together to Docxodus 12.4.1. Local, production, test, and remote-worker Compose stacks now use ghcr.io/open-source-legal/docxodus-service:1.2.0-docxodus12.4.1; the frontend pins the same library version with its updated Yarn lockfile.

The production build previously omitted the dynamically loaded WASM runtime. Include those assets with their original directory layout and give the renderer an explicit production path. The browser regression test now loads the built runtime without mocking its asset requests and checks rendered document text.

The service upgrade to .NET 10 and Docxodus 12.4.1 is already merged in docxodus-service#1, and the image publish workflow passed. Published image digest: sha256:e27dfbf8776bfa1ed8a7408f1ffe8632decf1e9582bbd7164d903226552abcc7.

Validation:

• Service CI and CodeQL passed; all 8 .NET integration cases passed, including Unicode annotation offsets.
• Pulled the published image and verified health, real DOCX parsing, and malformed-request handling. Its text, structural spans, and page/token metadata match the 12.4.1 npm WASM exporter on the OpenContracts fixture.
• yarn build passed (TypeScript and production bundle).
• WASM asset tests: 8 passed, including actual Vite build output and symlink exclusion.
• DOCX browser component tests: 8 passed, 1 pre-existing skipped test.
• Pre-commit and formatting checks passed.

[codecov]

Codecov Report

❌ Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...ponents/annotator/renderers/docx/DocxAnnotator.tsx	50.00%	0 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!