Add tETH to Core Instance Ethereum

The proposal follows Aave's standard governance pattern: a single on-chain action that delegatecalls execute() on a dedicated payload contract. The decoded calldata provides no visibility into the specific parameters (LTV, LT, caps, eMode settings, etc.) that this payload contract actually sets, since those are encoded in the contract's deployed bytecode rather than in the proposal's top-level calldata. As a result, I cannot directly verify the numeric parameters listed in the description (e.g., 0.05% LTV, 10,000 supply cap, 72% eMode LTV) against on-chain values from the JSON provided alone. The action target and function name (execute() on a governance payload contract) are consistent with the described intent of onboarding tETH to the Core instance and enabling a stablecoin liquid eMode, and there is nothing in the visible calldata that contradicts the description. However, because the actual parameter-setting logic is opaque at this level of decoding, confidence in a full line-by-line match is low. No discrepancies are flagged, as there is no evidence of mismatch, but a reviewer should ideally cross-reference the linked Solidity implementation file to confirm exact parameter values before relying solely on this analysis.