feat: non simd sha256 for incompatible systems

[matthewkeil]

Motivation

An issue was posted about systems that do not support simd feature set. Made library compatible with those systems.

See ChainSafe/lodestar#7177 for more information.

Description of Changes

• as-sha25
  • make common.ts that holds non-simd functionality
  • make simd and non-simd entrance files
  • call common from both entrance files and implement simd only in simd version
  • modify codegen and package scripts to build both versions of the code
  • modify TS wrapper code to load correct version of bindings depending on simd presence
  • modify TS wrapper code to call correct methods depending on presence of simd
  • fix tests to exercise both sets of bindings fully

[twoeths]

I don't see we're using simd sha256 in lodestar, we haven't enabled batch hash yet

Update: nvm, we haven't used but the wasm code was loaded anyway

[wemeetagain]

You should be able to use WebAssembly.validate to synchronously do "feature detection" and avoid a lot of complexity related to async initialization here.
(It appears that wasm-feature-detect is using WebAssembly.validate under the hood.)

eg:

import {wasmCode} from "./wasmCode.js";
import {wasmSimdCode} from "./wasmSimdCode.js";

const hasSimd = WebAssembly.validate(wasmSimdCode);

const _module = new WebAssembly.Module(hasSimd ? wasmSimdCode : wasmCode);

[wemeetagain]

LGTM!
looks like the repo also got linted?