Update PriceOracleSentinel

The proposal describes updating the PriceOracleSentinel implementation via setPriceOracleSentinel calls on four networks: Arbitrum, Optimism, Base, and Metis. The decoded on-chain actions are four forwardPayloadForExecution calls from the L1 cross-chain governance controller, targeting chain IDs 10 (Optimism), 42161 (Arbitrum), 1088 (Metis), and 8453 (Base) — exactly matching the four networks named in the description. This is the standard Aave cross-chain governance pattern: the top-level L1 proposal only forwards payloads to L2/L3 executors, which then execute the actual setPriceOracleSentinel calls referenced in the linked implementation contracts (AaveV3Optimism_UpdatePriceOracleSentinel, AaveV3Arbitrum_UpdatePriceOracleSentinel, etc.). Since we cannot inspect the bytecode of the destination payload contracts from this calldata alone, we cannot verify the exact new sentinel address deployed on each chain, but the structure (four networks, correct chain IDs, standard forwarding mechanism, and references to per-network implementation contracts matching the four named networks) is fully consistent with what the description claims. No values, targets, or omitted/extra actions stand out as suspicious at this level of decoding. Confidence is medium because full verification would require decoding the sub-payloads on each L2, which are not included here.