WASM dependency analysis

[lucacasonato]

To unblock https://github.com/denoland/deno/issues/2552, deno_graph needs to be able to represent WASM modules in a module graph. To do this, we need to parse out the import sections in a module, because with the ESM-WASM integration, these can reference other JS / WASM modules (and thus they need to be part of the module graph).

To do the analysis of the WASM modules we can probably use wasmparser. It is a streaming parser, so we don't waste compute cycles and memory getting an entire WASM AST just to extract the imports.

[lino-levan]

With https://github.com/denoland/deno_graph/pull/357 landing, what's the status of this?