Add assert cheatcodes

[tuturu-tech]

Add assert* cheatcodes: assertTrue, assertFalse, assertEq (6 type variants), assertNotEq (6 type variants), and assertLt/Le/Gt/Ge (8 comparison operators). Tested each, most assertions return Panic(0x01) on failure (assertFalse and assertTrue don't, I wasn't able to figure out why)

Testing:

• TestAssertCheatCodesPass: Verifies passing assertions work correctly
• TestAssertCheatCodesFail: Verifies failing assertions are detected and return panic code 0x01

TODO:

• Debug assertTrue and assertFalse

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[samalws-tob]

I thought callSequence would be the sequence we tried to execute, so the first one in the sequence could be the one that triggered the assertion failure, rather than the last one. If so, that could lead to these tests failing nondeterministically
Not sure how to test whether I'm right or not...

[samalws-tob]

Since these are all meant to not get an assertion failure, maybe we should group these into one big function so that we can be sure everything gets hit? Right now we might miss one because it doesn't get randomly generated in any of the sequences

[dguido]

Detailed review - the core implementation is solid and follows existing patterns well, but there are a few critical issues to address.

Must Fix

1. Error Swallowing in cheatCodePanicData

returnData, _ := panicMethod.Inputs.Pack(panicCodeBig)  // Error swallowed

If packing fails, returnData will be nil and the fuzzer returns corrupted panic data. Please handle the error:

returnData, err := panicMethod.Inputs.Pack(panicCodeBig)
if err != nil {
    logging.GlobalLogger.Panic("Failed to pack panic code for assertion cheatcode", err)
}

2. Test Reliability Issue

As @samalws-tob noted, the test relies on the last call being the failing assertion, but fuzzer-generated sequences are randomized. Consider checking any call in the sequence for panic code 0x01, not just the last one.

Recommended Improvements

3. Performance: Cache Panic Method

Creating a new abi.Method on every assertion failure is inefficient. Consider creating it once at initialization:

var panicMethod = abi.NewMethod("Panic", "Panic", abi.Function, "", false, false,
    abi.Arguments{{Type: typeUint256}}, abi.Arguments{})

4. Add Documentation

The cheatCodePanicData function lacks a doc comment explaining its purpose.

5. Defensive Nil Checks

Consider adding nil checks for comparison inputs:

if left == nil || right == nil {
    return nil, cheatCodeRevertData([]byte("assertLt: nil value provided"))
}

---

Overall the implementation demonstrates good understanding of the codebase architecture. Once these issues are fixed, this will be ready to merge.