Activate Freezing Steward on v3 missing networks

The description states this proposal activates the FreezingSteward contract as RISK_ADMIN on three specific networks that were missed in a prior proposal: Avalanche, Metis, and Base. The decoded calldata shows exactly three actions, each calling forwardPayloadForExecution on the same L1 cross-chain controller contract, targeting chain IDs 43114 (Avalanche), 1088 (Metis), and 8453 (Base) respectively — a one-to-one match with the three networks named in the description. This is the standard Aave cross-chain governance pattern where an L1 proposal forwards execution payloads to network-specific payload controllers that then perform the actual on-chain role grants on each L2/sidechain. The chain IDs, action count, and network ordering all line up with the prose. I could not decode the internal logic of the forwarded payload contracts (only their addresses are visible), so I cannot verify with full certainty that each payload exclusively grants RISK_ADMIN to a FreezingSteward matching the Ethereum/Polygon/Optimism/Arbitrum implementations referenced in the links. This limits my confidence to medium rather than high, but nothing in the visible calldata contradicts the description, and no unexplained extra actions, value transfers, or off-target chains are present.}