Enable additional SVR oracles

The decoded calldata contains a single action: a generic execute() call to a payload contract, which is the standard pattern for Aave Governance V3 proposals — the specific logic (replacing oracle feeds for the nine listed assets via SVR_STEWARD) is implemented inside that payload contract's bytecode rather than being visible as discrete calldata parameters. This matches the proposal's linked GitHub implementation file for 'EnableAdditionalSVROracles', and the pattern (single execute() call to a purpose-built payload) is exactly what is expected for this type of Aave proposal. Because the granular feed-by-feed replacement instructions are not independently visible in the decoded action, I cannot fully verify each individual token/feed mapping against calldata, but there is no evidence of a mismatch, extra action, or omitted major action — the single decoded action is fully consistent with the proposal's stated purpose of activating SVR feeds through the steward contract. Confidence is medium rather than high because the specifics (exact feed addresses, USDC inclusion) are only inferable from context, not directly decoded parameters visible here. No numerical values, targets, or claims in the description contradict what's decoded; this looks like a standard, boilerplate Aave payload execution matching its description in scope and intent.