feat: add userOpFailed hook

[BenSparksCode]

Changes:

• When a metacall fails due to the UserOperation call reverting with the UserOpFail error, the rest of the hooks are skipped, and Atlas executes an additional UserOpFailed hook.
• The UserOpFailed hook is called on the DAppControl, and includes the UserOperation memory userOp parameter as well as the relevant properties available via the appended packed Context var. DAppControls can implement this hook in the same way other hooks are implemented.
• The execution of the new UserOpFailed hook happens in the catch block of the metacall function. This means that any accounting changes that would have occured in _settle() are skipped.
• If the UserOpFailed hook reverts, the entire metacall will always revert.

To Do:

• Set gas limit for UserOpFailed hook - maybe specified in dAppOp.
• Add needsUserOpFailedHook() setting to CallConfig to make this new call conditional.
• Enforce needsUserOpFailedHook() and allowsReuseUserOps() settings are mutually exclusive.
• Check new errors are handled correctly in Simulator.
• Tests

[BenSparksCode]

Moving this "revert-prevention-for-refund" type of research to the monad-contracts repo. Will most likely not involve a new DAppControl hook.