Importing console_log should not break the WebAssembly Compoenent Model

https://github.com/bytecodealliance/wasm-tools/issues/2483

From what I can see, the WIT is fine and wasm-tools is doing the right thing, but the WAT being passed to watToWit does not match the naming scheme wasm-tools expects for the specified WIT interface. Specifically, wasm-tools expects an import named "console-log" from a module named "env" based on the declared name in the WIT file. Instead, it's finding an import named "console_log" from the module named "env" and doesn't know what to do with it.

WIT is intended to provide a human-readable representation of the Component Model type system, which does not cover every possible existing ABI and naming convention used in Wasm modules that exist in the wild. The expectation is that the module author (or binding generator) will have the Component Model "canonical" ABI and naming convention in mind when creating the application, which may require source code modifications.

I do recall there was a plan to eventually support other (i.e. "non-canonical") ABIs and/or naming conventions in the Component Model, but I'm not aware of any existing support for that in the specification or in wasm-tools.

Start with the linked wasm-tools issue 2483 and compare the WIT interface name with the env/console_log import described here. Determine whether the Component Model specification or wasm-tools defines support for non-canonical naming conventions; the issue is complete only when the expected behavior and scope of that support are decided.