feat(wasm): support text extraction within page regions

Summary

The napi binding lets you extract text from a specific page and region (pick a page, give it a bounding box, get the text back). The WASM package (@firecrawl/pdf-inspector-wasm) doesn't: it only does whole-document extraction (processPdf, extractText, classifyPdf, detectPdf, version), so it can't target a specific page and region.

Why it works

My current use case involves validating an uploaded PDF client-side by reading the text that sits at a specific position on a page. That maps directly to the region-based extraction the napi binding already offers, including the per-region signal when extraction looks unreliable. Without it in WASM, that kind of validation has to rely on whole-document output and loses the positional semantics.

Ask

Bring region-based text extraction to the WASM package.

Notes

• Feature request, not a bug.
• This would be handy for anyone with a similar case — thanks for the library and the features you already ship.

Start by comparing the WASM package exports—processPdf, extractText, classifyPdf, detectPdf, and version—with the existing napi binding's page-and-region extraction. Trace how the napi binding accepts a page and bounding box and reports per-region extraction reliability. Done means the WASM package can target a page region and expose the corresponding text and reliability signal.