Quark v2 changes

[kevincheng96]

Updating the quark-scripts repo to depend on the latest version of Quark (Quark v2). The main changes in this PR are:

• Update quark submodule to the latest commit on the Quark v2 branch
• Bump up Solidity version to 0.8.27 and EVM version to cancun
• Update QuarkOperation struct to the newest version that has a isReplayable field
• Update RecurringSwap.sol to no longer need a cancel function and no longer need to call allowReplay()
• Bring in the Cancel.sol core script, used for cancelling replayable operations
• Update QuarkBuilder to use Quark v2; add the new fields nonceSecret and totalPlays to QuarkBuilder
• Optimize QuarkBuilder to get rid of stack too deep errors from introducing the new fields

[kevincheng96]

There's a bunch of interface changes that need to be made in QuarkBuilder for the client to pass in a random nonce. I plan to do that as a separate PR.

[hayesgm]

lgtm

[hayesgm]

This is interesting, and I think correct. The Paycall operation is repalyable IFF what it wraps is replayable?

[kevincheng96]

Exactly. If it's a RecurringSwap using Paycall, then the Paycall itself has to be replayable.

[hayesgm]

Same here, so basically if it's wrap and replayableSupply this is now replayableWrapAndSupply?

[kevincheng96]

Yeah, if the last operation is replayable, the merged operation should be replayable.

[kevincheng96]

The latest commit (fc9d209) rebases on main and applies the Quark v2 changes to the newest MorphoClaimRewards action. After the rebase, we were hitting stack too deep errors again, so the commit also includes some optimizations to the QuarkBuilder code.

EDIT: Replaced that commit with e5e823c, which now just comments out the MorphoClaimRewards logic since it is currently unused. The root cause for the stack too deep errors is the yul optimizer. The optimizer will inline some of the internal function calls in the QuarkBuilder, causing stacking too deep issues. The way to fix this is to turn off the optimizer for the QuarkBuilder. However, since the Quark scripts should still be built with the optimizer on, there's not a good way to separate the compilation settings unless we split QuarkBuilder into its own foundry project.