Sync emergency admin on v2 AMM

The proposal description states a single, narrow action: calling setEmergencyAdmin on the Aave v2 AMM PoolAddressesProvider to align it with the Aave Ethereum Guardian address. The decoded calldata shows one action, forwardPayloadForExecution, which is the standard entry point used by Aave Governance v3 proposals to submit a previously deployed 'payload' contract (here at address 0xdAbad81aF85554E9ae636395611C58F7eC1aAEc5) for execution. This forwarding pattern is boilerplate for all Aave BGD-style proposals of this era — the actual setEmergencyAdmin logic lives inside the payload contract being forwarded, which is not itself decoded in the provided data. Because the decoded action is consistent with the expected governance architecture (a single payload forward, access level 1, matching a maintenance-type proposal) and there is no evidence of a different target, value, or conflicting action, I found no direct value or target mismatch. However, since the actual setEmergencyAdmin call is not visible in the decoded arguments (it's nested inside the forwarded payload contract), full verification of the exact recipient address and function is not possible from calldata alone — this limits confidence to medium rather than high. No omissions, extra claims, or misleading phrasing were identified given the information available; the proposal appears consistent with a standard governance forwarding call implementing the described change.