Throw error when WASM memory limit is reached

[45930]

Relates to: #1214 (memory leak + not handling OOM well is a recipe for disaster)

User reports node thread hangs after some number of iterations of recursive proving: https://discord.com/channels/484437221055922177/1326949912759500861

When WASM reaches it's memory limit, we should surface this in o1js. Current behavior is that the thread stays active, but cannot do any proving. Desired behavior is to throw an error letting the developer know they are out of WASM memory.