Wait for WASM runtime before running function-search worker

[VA00]

Motivation

• Prevent a crash where the worker calls into WASM before Emscripten runtime helpers (e.g. _emscripten_stack_get_current) are available.
• Ensure function-search messages received early are not lost and do not trigger invalid ccall usage.
• Make the worker robust to messages arriving before vsearch.js has finished initializing.

Description

• Update calculator_frontend/public/wasm/worker_function.js to add a runtimeReady flag and a pendingMessages queue.
• Add Module.onRuntimeInitialized handler that sets runtimeReady, posts a ready message, and flushes queued messages by calling handleWork.
• Refactor the worker entry to use handleWork for processing work and wrap the original onmessage to queue messages until runtime readiness.

Testing

• No automated tests were run for this change.
• Runtime behavior was adjusted so the worker waits for Module.onRuntimeInitialized before invoking WASM entrypoints, eliminating the previously observed _emscripten_stack_get_current error in prior runs.

---

Codex Task