Increase cbBTC Supply Caps

The proposal describes two concrete parameter changes: raising the cbBTC supply cap to 10000 on Aave V3 Ethereum and to 5000 on Aave V3 Base. The only decoded on-chain action is a call to execute() (a fallback function with no arguments) on what appears to be an Aave governance payload/controller contract on Ethereum. This matches the well-known Aave V3 cross-chain governance pattern, where the actual parameter-setting logic (setSupplyCap calls, and the cross-chain message to Base) is hard-coded inside the payload contract rather than passed as calldata arguments to the governance executor. Because the calldata gives no visibility into the payload's internal logic, it is not possible to directly verify that the exact cap values (10000 and 5000) match what the contract will set, nor to confirm the Base-side action is included. However, this opacity is expected and routine for this proposal type (as referenced by the linked BGD Labs implementation and test files), not evidence of a mismatch. No contradictory targets, values, or omitted high-level actions are visible in the decoded data. Given the inability to inspect the payload internals, confidence in a full value-level comparison is low, but nothing in the available data contradicts the description, so the assessment is 'consistent' rather than flagging an unverifiable discrepancy.