shouldRequestWasmRespawn classification

Trap: classifying native ONNX Runtime failures from Error.message alone looks sufficient, but Node often stores ERR_DLOPEN_FAILED only in error.code; common wrong ELF class, missing GLIBC_*, Windows %1 is not a valid Win32 application, and versioned Darwin Library not loaded forms then bypass WASM fallback. Fix: classify the error object, requiring a native ORT artifact plus a loader code/message, and permit exactly one fresh forced-WASM worker; unrelated or repeated failures remain terminal.