Introduce transaction epilogue

[frisitano]

This PR implements the transaction kernel epilogue. The scope of this PR includes the following:

• Introduction of make watch command that allows cargo watch to monitor the assembly directory miden-lib/asm and rebuild the miden library when a file change is saved. This dramatically improves developer experience when working with the debugger making quick iterative changes.
• Introduction of masm transaction epilogue. The final check to assert the invariant of assets between start and end of the transaction is still outstanding and is waiting on the completion of SMT implementation.
• Introduction of an assembly utils module for shared code. This has been useful and I suggest we create a memory module that we can use to handle all memory related activities. I think this should also allow us to centralise the constants we use as most (maybe all?) of them are related to memory.
• Introduction of rust based memory module that specifies the memory layout for the miden kernel.
• Refactor of the test suite and common modules.
• Change max assets per note to 256
• Introduction of ExecutedTransaction object which holds all information relating to a transaction.
• Introduction of transaction/utils.rs which holds common functionality for producing commitments and inputs / outputs for a transaction.
• Introduction of Metadata to the Note object.

[bobbinth]

Looks great! Thank you! I left some questions and comments inline.

[bobbinth]

Looks good! Thank you! I left a few more comments inline. A couple of other things:

1. This should probably be updated to work with the latest next branch of Miden VM.
2. In the future, once things stabilize a bit more, we should write an article in the docs to document memory layout with diagrams and in-depth explanations. Let's create an issue for this.

[bobbinth]

Looks good! Thank you! I left one comment about the nonce - once it is addressed, we should be good to merge.

[bobbinth]

I was thinking we'd check only the input value (not the nonce itself). So, it would look like:

export.incr_account_nonce
    u32assert.1
    padw push.ACCT_ID_AND_NONCE_PTR mem_loadw
    movup.4 add
    push.ACCT_ID_AND_NONCE_PTR mem_storew dropw
end

I'm not sure we should restrict the nonce to be 32 bits.

[frisitano]

got it, makes sense!