Deno doesn't report Wasm stack traces correctly

For example running the `other.test_symbol_map_O2` test we this from node:

```
Error
at run_js (/usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:7527)
at wasm://wasm/f0d79f0e:wasm-function[4]:0x140
at 1069 (/usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:7492)
at runEmAsmFunction (/usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:6491)
at _emscripten_asm_const_int (/usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:6554)
at wasm://wasm/f0d79f0e:wasm-function[5]:0x150
at callMain (/usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:8399)
at doRun (/usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:8803)
at run (/usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:8957)
at removeRunDependency (/usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:5927)
```

But this from deno:

```
Error
at run_js (file:///usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:7748)
at (wasm://wasm/4b6c7e0a:1:321)
at Object.1069 (file:///usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:7713)
at runEmAsmFunction (file:///usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:6712)
at _emscripten_asm_const_int (file:///usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:6775)
at (wasm://wasm/4b6c7e0a:1:337)
at callMain (file:///usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:8620)
at doRun (file:///usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:9024)
at run (file:///usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:9178)
at removeRunDependency (file:///usr/local/google/home/sbc/dev/wasm/emscripten/out/test/a.out.js:1:6148)
```

note the `wasm://wasm/4b6c7e0a:1:321` vs `wasm://wasm/f0d79f0e:wasm-function[4]:0x140` in the second line.