public-vm(simulator): Journal should keep track of reverted state

[Maddiaa0]

Overview

When a call reverts in the journal, its current behaviour drops it essentially making it such that the state updates never occured.

This is perfectly fine for a native implementation; however we still need to prove memory accesses as they occur, as we later need to prove that they took place in the storage read validation circuit ( in the vm or later in the vm).

The journal should have another section, or sub journal. That keeps track of reverted state seperately to the state we want to commit to the world state at the end of block execution.

Depends on

• public-vm(simulator): Journal should keep track of reads #3999

Links

• https://yp-aztec.netlify.app/docs/public-vm/avm
• Original journal pr: feat(public-vm): avm journal #3945