Increase CCIP Facilitator Capacity

The proposal follows Aave's standard 'Direct-to-AIP' governance pattern: a single payload contract is deployed with the specific logic (e.g., increasing GHO bucket capacity and bridgeLimit) hard-coded into its execute() function, and governance simply calls execute() on that contract. The decoded calldata here shows exactly this pattern — one action, target on Ethereum mainnet, function 'execute()' with no arguments, matching the referenced implementation contract style used by bgd-labs payloads. Because the payload's internal logic (the specific capacity/bridgeLimit values) is not exposed in the decoded arguments, I cannot directly cross-check the '1M to 2.5M' and 'bridgeLimit' figures against on-chain data from this calldata alone. However, there is nothing in the calldata that contradicts the description, and the structure (single execute() call to a mainnet payload contract) is exactly what this type of proposal looks like. Given the lack of visibility into the payload's internal state changes, I mark confidence as low rather than asserting a discrepancy — there is no evidence of mismatch, only insufficient decoded detail to fully confirm the specific numbers. No omissions, target mismatches, or misleading phrasing were identified based on the available data before rendering a verdict.