Merge pull request #1655 from MSilb7/data-fpresolve

Add Dispute Game Resolve Logic

Author: krofax

pages/app-developers/tools/data-and-dashboards/data-glossary.mdx

@@ -49,6 +49,7 @@ This glossary is a living document and will be updated over time as new metrics
 *   **Transaction Batches:** All transactions where the transaction from address is the `batcherHash` address and the transaction to address is the `batchInbox` as defined in the chains' `SystemConfigProxy` contract.
 *   **State Output Submissions or Dispute Games:** All transactions where the transaction from address is the `Proposer` and the transaction to address is either the `outputOracleProxy` or the `disputeGameFactoryProxy` as defined in the chains' `SystemConfigProxy` contract.
 *   Each chain's `SystemConfigProxy` contract can be found in the Superchain Registry.
+*   **Resolving Dispute Games:** All transactions sent to dispute game contracts created by the `disputeGameFactoryProxy`, where the transaction's method id (function call) is either `Resolve`, `ResolveClaim`, or `ClaimCredit`.
 
 **Why it matters:**