increase supply cap for cbETH Aave Ethereum V3

The proposal follows the standard Aave governance payload pattern: a single on-chain action invoking execute() on a payload contract address, with the actual logic (setSupplyCap for cbETH to 30,000) defined in the linked Solidity source rather than decoded as explicit calldata arguments. This is typical for Aave AIPs, where the executor contract's bytecode is verified off-chain via the published source and audit (BGD Labs), and the decoded action list will always show just 'execute()' with no arguments regardless of the underlying logic. The description's claim (raise cbETH supply cap from 20K to 30K) matches exactly the CBETH_SUPPLY_CAP constant (30_000) in the provided contract source. There is no value, target, or omission discrepancy detectable from the available data. Confidence is medium rather than high because the decoded calldata itself does not expose the setSupplyCap call parameters directly — verification relies on trusting the linked source code matches the deployed bytecode, which is standard practice for Aave payloads but not independently confirmable from the JSON alone.