Update syrupUSDC liquidation protocol fee

The proposal describes two concrete on-chain changes: (1) raising the Liquidation Protocol Fee for SyrupUSDC on Aave V3 Base from 0% to 10%, and (2) a correction to PT srUSDe e-mode labels. The only decoded on-chain action is a single execute() call (decoded as an unparameterized fallback) to what is presumably an Aave governance payload contract. This is the typical top-level pattern for Aave AIPs: the mainnet action just triggers execution of a payload contract, and the granular state changes (like reserve parameter updates) happen inside that payload's own logic, which is not exposed in this decoded action list. Because the decoded calldata carries no arguments or sub-call details, there is no way to directly verify or contradict the specific 10% fee value or the e-mode label correction against on-chain data. I found no direct contradiction — the single action is consistent with 'execute a governance payload that updates Aave V3 Base configs' — but the lack of granularity means confidence in this comparison is low. No values, targets, or omissions could be confirmed as mismatched given the information available, so I am not flagging any discrepancies, but flagging low confidence so reviewers know this analysis could not verify the specific numeric claims.