Convention and tools for library authors exporting wasm modules

[pi0]

Currently, the npm state is chaotic as each maintainer decided and went with a different path of how exporting (or internally using) wasm modules.

The idea is to provide docs + probably basic CLI tools to make it a little more standard/predictable and optimizable (for example in a way that we don't double bundle WASM files once inlined and once externalized)

More of compatibility with those packages that stick with legacy APIs, can be covered with Runtime Utils (https://github.com/unjs/unwasm/issues/4)