Add RPL to Aave V3 Ethereum pool

The proposal follows Aave's standard governance pattern: the on-chain action is a single delegatecall-style execute() invocation on a dedicated payload contract, referenced in the proposal's 'Implementation' link. The actual listing parameters (supply/borrow caps, rate curve, reserve factor, liquidation fee, collateral/borrow flags) are encoded inside that payload contract's bytecode and are not visible in the decoded calldata itself — only a generic fallback/execute() call with no arguments is decoded. This is the expected, routine structure for Aave V3 listing proposals, and there is nothing in the decoded action that contradicts the description (e.g., no unexpected target, no value transfer, no additional calls). However, because the decoded calldata provides no visibility into the specific numeric parameters (caps, rates, fees) that the payload contract will apply, a reviewer cannot independently verify that these exact figures match the description from the calldata alone. This limits confidence in a full parameter-by-parameter comparison, but does not by itself constitute a discrepancy — it reflects an inherent limitation of decoding a proxy/payload execution pattern rather than evidence of a mismatch. No value, target, or action omissions/additions were identified within the scope of what is decodable.}