Add ERC20CommerceEscrowWrapper event indexing to payments-subgraph

[MantisClone]

Problem

Commerce payments use HTTP polling (contract.on()) to detect blockchain events. Events during API downtime (deployments, crashes, restarts) are permanently lost, causing webhook delivery failures and database inconsistencies.

Proposed Solution

Add ERC20CommerceEscrowWrapper contract indexing to the existing payments-subgraph repository (Base and Base Sepolia networks).

Schema: New CommercePayment entity with events (PaymentAuthorized, PaymentCaptured, PaymentVoided, PaymentRefunded). Separate from existing Escrow entity due to different state model.

Handler Pattern: Follow existing erc20EscrowToPay.ts pattern - handlers for each event type updating CommercePayment entity and creating CommercePaymentEvent records.

Deployment: Add datasource to subgraph.base.yaml and subgraph.sepolia.yaml with contract addresses from request-api environment config.

Considerations

• Contract deployment blocks needed for Base and Base Sepolia
• Schema design: separate CommercePayment entity vs extending existing Escrow entity
• Deployment coordination: payments-subgraph must be deployed before request-api can integrate

[MantisClone]

We should have this, but the main benefit is for Merchants who specify an Operator address that is not a Request Smart Account that has been delegated to the Request API for execution.

Not needed for intial launch, but we should still do it eventually.

[MantisClone]

Upon re-discussion, we realized that this is needed, even for Operators who are Request Smart Accounts because the API status tracking - it won't allow you to capture until it's detected the authorization is successful.