Fix WASM initialization retries

[melonamin]

What changed

• use one coherent WASM initialization lifecycle instead of a second analyzer-level rejected-promise cache
• allow a later call to retry after transient initialization failure
• guard reset and concurrent initialization so stale completions cannot repopulate cleared state
• add regression coverage for retry, concurrency, reset, and analyzer calls

Why

A failed first initialization was cleared by the loader but remained cached by the analyzer, permanently poisoning later analysis, completion, and export calls in the process.

Validation

• mise x node@20.20.2 yarn@1.22.19 -- yarn workspace @pondpilot/flowscope-core test
• mise x node@20.20.2 yarn@1.22.19 -- just check
• Codex review: no actionable findings

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!