Fix: Update OPFaultGameFinder to support Base Azul (game type 621)

[adraffy]

• updated OPFaultGameFinder
  • try IDisputeGame.l2SequenceNumber() before l2BlockNumber()
  • changed _isUnchallenged() to react to gameType
  • added IAggregateVerifier interface
  • added OPFaultParamTuple type
• changed default RPCs to dRPC instead of Ankr

---

Unfortunately, this parent game check is O(n^2) if any parent was successfully challenged:

function _isUnchallenged(...) {
    if (gameType == GAME_TYPE_AGGREGATE_VERIFIER) {
        for (;;) {
            uint256 status = gameProxy.status();
            if (status == GAME_STATUS_DEFENDER_WINS) {
                return true;
            } else if (status == GAME_STATUS_CHALLENGER_WINS) {
                return false;
            }
            address parent = IAggregateVerifier(address(gameProxy)).parentAddress();
            if (parent == address(0)) {
                return false;
            } else if (parent == address(params.asr)) {
                return true;
            }
            gameProxy = IDisputeGame(parent);
        }

---

• https://status.base.org/incidents/lj9f7jhbb2ys
• https://docs.base.org/base-chain/specs/upgrades/azul/overview#proofs

[clowestab]

For GAME_TYPE_SUCCINCT, if claimData() reverts or the return data cannot be decoded (undisclosed code change in update for example), this silently falls through to the generic fault-game checks, which would still likely fall through to the false return at the end of the block, BUT out of an abundance of caution/for clarity i think it'd be worth explicitly returning false within the catch block OR better explicitly having and else block for the default and then having the default return outside of the condition gate.

[clowestab]

This keeps this generic with the game type check but I suspect that over time OP and Base will diverge further with their codebases so semantically clearer file names and separations might be necessary.|

Full support for 621 i think is implicit, as ultimately the challenge state check is what is required regardless of the proving mechanism through which it is set.

Added one actionable comment, but otherwise looks good.