Support to link all wasm modules to a single .wasm (exe) file

[dumganhar]

Some References:

https://pspdfkit.com/blog/2022/dynamic-linking-in-webassembly/

https://qa.fmod.com/t/linking-fmodstudio-bc-to-emscripten-build/15392/7

In October of 2019 the emscripten SDK deprecated the “fastcomp” build process, which built all WebAssembly code as LLVM intermediate bit code (.bc files) and the linking/final processes converted the desired LLVM bit code into 32-bit WebAssembly byte code. All emscripten releases from 1.39 onward now use the “upstream” build process, where the clang compiler and LLVM tools all work with WebAssembly byte code directory.

https://emscripten.org/docs/compiling/WebAssembly.html#backends

[dumganhar]

• Put Spine wasm and physX wasm together ( the whole package size could reduces 80 KB )
• Put Box2D, Spine, physX wasm together( the whole package size could reduces (3500761 - 3317999 = 182KB)

EMSDK 3.1.41

Original Size:

• spine.wasm: 449470
• spine.wasm.js: 55547
• box2d.release.wasm.wasm: 183535
• box2d.release.wasm.js: 62299
• physx.release.wasm.js: 63643
• physx.release.wasm.wasm: 2686267

Fat wasm size:
spine+physX.wasm: 3103482
spine+physX.wasm.js: 65703
spine+physX+box2d.wasm: 3252061
spine+physX+box2d.wasm.js: 65938

[dumganhar]

Moved to sprint 10