[SVC-01M] Inexistent Prevention of Data Corruption

[pde-rent]

Recommendation:

We advise the StrategyV5Chainlink::setPriceFeed function to ensure that the feedByAsset[_address] entry is zero, and to utilize a different variable to track whether the _feed has been configured to be validated as such.

Acknowledged - This function is used to update an asset price feed, so we purposely won't revert if a previous feed already exists in the mapping.
eg.: USDC price feed is used for USDCe, up until a USDCe dedicated price feed goes live, and we're better off using this one that factors-in the bridge risk

[omniscia-core]

Utilizing a USDC price feed for USDCe (or generally any price feed for the underlying asset of a wrapped variant) is something we strongly advise against as there is never parity between the assets. The same goes for utilizing stablecoin evaluations based on the US Dollar, as 1 USDC != 1 USDT != 1 DAI != 1 USD.

[pde-rent]

Of course stables should never be assumed stable (ad. USDC == USD is indeed a wild claim every DeFi builder knows this), however when is comes to bridged USDC, aka USDC-e, when a price feed is non existent, the best polyfill for it remains the canonical USDC as the only other way would be to get its price from an LP (eg. Uniswap's) which we don't like to depend on (the DEX or its pool could be compromised easier than Chainlink/Pyth's feed, making it a less trustworthy source).
I agree that this is sub-obtimal, we should be able to get feeds for all our inputs