Use dwarf_to_json.wasm

[yurydelendik]

Attempt to fix #8948. It switches wasm-sourcemap.py to use nodejs (to run dwarf_to_json.wasm) that generates map/JSON. I tried to preserve all wasm-sourcemap.py's extra logic.

TODO is: fix rest of the toolset and testing to not rely or specify llvm-dwarfdump as wasm-sourcemap.py dependency.

[kripken]

I think instructions for where the Rust code is, and how to build it, would be enough. Checking in the wasm binary would be like how we check in the Java binary for Closure Compiler, as long as we know where the upstream is, that's fine.

@yurydelendik can you please elaborate more on what is blocking this PR, I'm not sure I understood from your comment in the original issue?

[yurydelendik]

can you please elaborate more on what is blocking this PR, I'm not sure I understood from your comment in the original issue?

there is a todo:

• fix "test_wasm_sourcemap" and "test_wasm_sourcemap_dead" tests (see e.g.

  emscripten/tests/test_other.py

  Line 8765 in f02ba54

  '--dwarfdump-output',

  ) to not use --dwarfdump-output

[yurydelendik]

binaryen supports DWARF nowadays -- closing in favor of that