Add Cooperative Storage

[hayesgm]

This patch adds back cooperative storage, which simply isolates each read and write call in QuarkScript to pulling the active nonce and isolating storage keys on that value.

Notes:

• This is cooperative. A malicious script is free to change any stored data.
• After a nested quark operation, the nonce value is cleared and thus will not be properly read. We raise an error in this case.

[kevincheng96]

• After a nested quark operation, the nonce value is cleared and thus will not be properly read. We raise an error in this case.

An alternative approach to address this would be to, in the wallet, cache the current activeNonce and set it back to this value after the callcode. Not saying we should do this, but in a tstore world this is basically free and would remove this weird edge case. It's basically what we used to do in the QuarkStateManager.

[kevincheng96]

LGTM

[hayesgm]

• After a nested quark operation, the nonce value is cleared and thus will not be properly read. We raise an error in this case.

An alternative approach to address this would be to, in the wallet, cache the current activeNonce and set it back to this value after the callcode. Not saying we should do this, but in a tstore world this is basically free and would remove this weird edge case. It's basically what we used to do in the QuarkStateManager.

Yeah, though scripts could also cache it themselves. Mostly here I want the scripts to be written pretty seamlessly, but they are free for more complex behaviors if they want to handle nested calls.