ensure acvm.js properly handles errors

[ludamad]

e2e tests are being observed to run for multiple hours in some failure cases where lots of output is presented. A specific instance for reference can be found here.

The core problem is error handling in the acvm.js component, but this is a problem in general if we print continuous output.

Key Points:

1. The e2e container doesn't seem to exit upon encountering an error in the test. The error seen might be getting swallowed instead of being propagated
2. The continuous noise from Anvil in the output prevents the 10-minute kill switch from terminating the test.

Actions to do or break-out into new issues:

• Ensure proper error propagation, especially concerning the wasm simulator error. Can change line 710 of acvm_js.js to throw an error and observe the behavior above, potentially running with --detectOpenHandles.

Done

• Silence Anvil output.

[charlielye]

Also, just a quick bit of envelope math, if all our e2e tests wait for the full 3hr timeout:
60m*3hr*20credits*34tests / 25000credits_per_pack * $15per_pack = $73 for a single run of the workflow.
Ouch.