feat: update approach to generating wasm

[tplooker]

Description

This PR makes several changes to how the WASM module in this library is generated.

• The WASM outputted by wasm-pack now defaults to a web compatible ES module and esm is used to translate this to Commonjs that is capable of being consumed by NodeJS.

• The default serving/loading of the WASM in web environments is now a more efficient style of loading that does not involve bas64 encoding the WASM reducing bloat.

• support for NodeJS 10 which is now EOL has had to be dropped due in compatibility with TextEncoder/TextDecoder that is used in the translated ES module.

• Support for ASM.js has now been dropped due to:

  1. It being incredibly slow
  2. It significantly bloating the package size
  3. Complicating the module loading logic
  4. Support for WASM in browser is ever-improving and for those wanting to use the package in RN environments should be consuming it via a native module.

• Tests for the changes have been added (for bug fixes / features)

• The commit message(s) follow conventional commits

• Documentation has been added / updated (for bug fixes / features)

• Changes follow the contributing document.

Motivation and Context

See above

Does this PR introduce a breaking change?

• Yes
• No

Which merge strategy will you use?

• Squash
• Rebase (REVIEW COMMITS)