Tests silently pass on Wasm memory errors

[samestep]

While working on #112, I occasionally ran the tests while a bug was causing the generated Wasm to access memory addresses larger than the allotted size of the memory. In this case obviously the tests should fail, but it seemed like Vitest was instead just immediately aborting and giving an exit code of zero, indicating success.