Add FXS to Ethereum V3

The proposal's on-chain footprint is a single generic call to the Aave governance v3 'forwardPayloadForExecution' function, which merely dispatches a pre-built payload (identified by id 1) to an executor contract for execution. The actual reserve-listing logic for FXS (supply/borrow caps, LTV, liquidation parameters, interest rate curve, etc.) lives inside that forwarded payload contract and is not itself decoded in the provided calldata. This means I cannot directly verify the specific numeric parameters (35% LTV, 45% LT, 800k supply cap, etc.) against on-chain calldata — they are asserted only in the payload's source code referenced in the description, not visible here. However, the high-level action (forwarding a payload to add FXS to the Aave V3 Ethereum pool) is fully consistent with the description's stated purpose, and there is nothing in the decoded action that contradicts or extends beyond what the description claims (e.g., no unrelated transfers, role grants, or upgrades). Because the decoded calldata is opaque about the granular parameters, my confidence in a detailed parameter-by-parameter comparison is low, but at the level of what can be verified, the action is consistent with the description's intent.