Disallow -sWASM_WORKERS with sanitizers

Back in emscripten-core#21701 I broke move the creation of wasmOffsetConvert and
wasmOffset into runtime_pthread.js but I didn't update
libwasm_worker.js which still uses the old name `wasmOffsetData` in its
initial post message.

When trying to update this just now I noticed that the offset converter
(and santiizers in general) don't seem to work on WASM_WORKERS so this
change simply disables them.

Author: sbc100

src/lib/libwasm_worker.js

@@ -204,12 +204,6 @@ if (ENVIRONMENT_IS_WASM_WORKER
 #endif
       'sb': stackLowestAddress, // sb = stack bottom (lowest stack address, SP points at this when stack is full)
       'sz': stackSize,          // sz = stack size
-#if USE_OFFSET_CONVERTER
-      'wasmOffsetData': wasmOffsetConverter,
-#endif
-#if LOAD_SOURCE_MAP
-      'wasmSourceMapData': wasmSourceMap,
-#endif
     });
     worker.onmessage = _wasmWorkerRunPostMessage;
 #if ENVIRONMENT_MAY_BE_NODE

tools/link.py

@@ -1556,6 +1556,8 @@ def limit_incoming_module_api():
     diagnostics.warning('emcc', 'output suffix .js requested, but wasm side modules are just wasm files; emitting only a .wasm, no .js')
 
   if options.sanitize:
+    if settings.WASM_WORKERS:
+      exit_with_error('WASM_WORKERS is not currently compatible with `-fsanitize` tools')
     settings.USE_OFFSET_CONVERTER = 1
     # These symbols are needed by `withBuiltinMalloc` which used to implement
     # the `__noleakcheck` attribute.  However this dependency is not yet represented in the JS