[non-emscripten] Split Node-API implementation by different feature about emnapi HOT 1 CLOSED

After a period of thinking and exploration, I think it is difficult to do this without making breaking changes. The fundamental reason is that emscripten and non-emscripten build targets share the same set of source code, and the function implementation requires access to wasm module related symbols, such as wasmMemory, wasmTable, etc., using the same set of source code means that the same is true for non-emscripten runtime. All Node-API function implementations must exist in a closure (createNapiModule) that can access these symbols. So it is difficult to split each function implementation into other top-level exported functions. Unless a completely new API is redesigned for non-emscripten without using the same source code. Another way is to use TypeScript custom transformers to do more magic, but this will increase the complexity. It is not worth doing just for tree shaking. For example, it is reasonable for projects like napi-rs to fully import emnapi's implementation.

from emnapi.