refactor(compiler-cli): gate synchronous preprocessor APIs on synchronous hosts - #71919

…or and HybridCompiler

Bundler integrations and workspace reconfigurations can change how module
specifiers resolve without editing any individual source file—for example
when alias tables, export conditions, or package layouts change between
builds. While `invalidate_module_resolution` re-runs previously failed
resolutions after file creation or deletion, callers also need a way to
flush positive cached resolutions without discarding parsed ASTs.

Add `ResolutionCache::clear_all` and `QueryEngine::clear_resolution_cache`
to clear both host-internal and engine-level resolution caches and evict
queries derived from any importer's resolutions while preserving cached
`ParseFile` results. Expose `clear_resolution_cache` on `Analyzer`,
`TestAnalyzer`, `WasmAnalyzer`, and the sidecar JSON-RPC server, returning
the deduplicated list of stale module IDs while preserving virtual module
IDs verbatim instead of normalizing backslashes.

Surface `clearResolutionCache` on `IAnalyzer`, `WasmAnalyzer`,
`NapiAnalyzer`, `SidecarAnalyzer`, and `HybridCompiler`. In `HybridCompiler`,
sequence `clearResolutionCache` through the serialized update queue so
evicted analyses are dropped from the TypeScript file cache, recorded for
incremental emit, and refreshed on the following delta pass.

…processor pump loop

Previously, `WasmAnalyzer.getMetadataForFile` called the synchronous
`getMetadataForFile` WASM export directly, stepping the query engine to
completion inside a single FFI call. When an asynchronous `AnalysisHost`
suspends module resolution or content loading across JavaScript round-trips,
blocking inside a single WASM export cannot yield back to the host.

Add `ModuleRef` and `QueryEngine::get_metadata_for_file_id` (tracking whether
`ParseFile` loaded a module on `ParsedFileOwner::loaded` so missing modules
return `None` under asynchronous hosts just as they do under `DefaultFsHost`).
Expose `Analyzer::request_metadata_core` and `WasmAnalyzer::request_metadata`,
emitting `metadataResult` events from `WasmAnalyzer::pump` as oneshot queries
settle.

Update the TypeScript `WasmAnalyzer` adapter so `getMetadataForFile` registers
a pending request via `request_metadata` and resolves through `pumpLoop`
alongside active analysis streams, while cleaning up in-flight requests when
`close()` is called.

…nous hosts

Asynchronous bundler hosts suspend module resolution and content loading across
pump turns, so synchronous `*_blocking` and FFI entry points cannot run to
completion within a single call. Without explicit host gating, calling a
synchronous entry point against an asynchronous host panics inside WASM or NAPI
instead of reporting the host constraint cleanly.

Enforce `AnalysisHost::is_synchronous` inside `QueryEngine::block_on_query` and
add fallible `ensure_synchronous_host` checks to `Analyzer`'s synchronous core
helpers. Convert `WasmAnalyzer::get_metadata_for_file` and `read_resource` to
return `Result<Option<String>, String>` and expose `is_synchronous_host` on
WASM bindings so synchronous WASM calls fail cleanly with
`"synchronous APIs require a synchronous host"` instead of panicking.

Expose `isSynchronousHost` (and `WasmAnalyzerOptions::isSynchronousHost`) on
`WasmAnalyzer` while keeping asynchronous WASM mutation and template-lookup
calls working when `isSynchronousHost` is `false`. Behavior under
`DefaultFsHost` is unchanged.