Remove wormhole references

[XapaJIaMnu]

Should fix #421
I am not sure if the import intgemm as a separate step is still a thing though.

[jelmervdl]

There's the try linking to mozilla's native intgemm bit, but I don't think there's any wormhole code in the module itself.

bergamot-translator/wasm/module/worker/translator-worker.js

Lines 248 to 253 in ca95467

	WebAssembly.instantiateStreaming(response, {
	...info,
	'wasm_gemm': this.options.useNativeIntGemm
	? this.linkNativeIntGemm(info)
	: this.linkFallbackIntGemm(info)
	}).then(({instance}) => accept(instance)).catch(reject);

I don't think we ever had a wasm binary that didn't use SIMD instructions to support very old machines for which Firefox doesn't support those. (But I don't know if Firefox supports those machines anyway anymore)

[kpu]

There's the try linking to mozilla's native intgemm bit, but I don't think there's any wormhole code in the module itself.

bergamot-translator/wasm/module/worker/translator-worker.js

Lines 248 to 253 in ca95467

	WebAssembly.instantiateStreaming(response, {
	...info,
	'wasm_gemm': this.options.useNativeIntGemm
	? this.linkNativeIntGemm(info)
	: this.linkFallbackIntGemm(info)
	}).then(({instance}) => accept(instance)).catch(reject);

I think some form of that is intended for production. At least, they sent me a rewrite of intgemm for multiple architectures.

I don't think we ever had a wasm binary that didn't use SIMD instructions to support very old machines for which Firefox doesn't support those. (But I don't know if Firefox supports those machines anyway anymore)

Agreed, we didn't. And if we did, it would have been to support Safari, which we decided to wait on until they added SIMD...