Vulnerability: Incorrect deviation calculation in isDeviatingWithBpsCheck function
Severity: medium

Description:
The current implementation of the `isDeviatingWithBpsCheck` function in the codebase leads to inaccurate deviation calculations, potentially allowing deviations beyond the specified limits.\\nThe function `isDeviatingWithBpsCheck` checks if the deviation between two values exceeds a defined threshold. This function incorrectly calculates the deviation, considering only the deviation from the larger value to the smaller one, instead of the deviation from the mean (or TWAP).\\n```\\n    function isDeviatingWithBpsCheck(\\n        uint256 value0_,\\n        uint256 value1_,\\n        uint256 deviationBps_,\\n        uint256 deviationMax_\\n    ) internal pure returns (bool) {\\n        if (deviationBps_ > deviationMax_)\\n            revert Deviation_InvalidDeviationBps(deviationBps_, deviationMax_);\\n\\n        return isDeviating(value0_, value1_, deviationBps_, deviationMax_);\\n    }\\n\\n    function isDeviating(\\n        uint256 value0_,\\n        uint256 value1_,\\n        uint256 deviationBps_,\\n        uint256 deviationMax_\\n    ) internal pure returns (bool) {\\n        return\\n            (value0_ < value1_)\\n                ? _isDeviating(value1_, value0_, deviationBps_, deviationMax_)\\n                : _isDeviating(value0_, value1_, deviationBps_, deviationMax_);\\n    }\\n```\\n\\nThe function then call `_isDeviating` to calculate how much the smaller value is deviated from the bigger value.\\n```\\n    function _isDeviating(\\n        uint256 value0_,\\n        uint256 value1_,\\n        uint256 deviationBps_,\\n        uint256 deviationMax_\\n    ) internal pure returns (bool) {\\n        return ((value0_ - value1_) * deviationMax_) / value0_ > deviationBps_;\\n    }\\n```\\n\\nThe function `isDeviatingWithBpsCheck` is usually used to check how much the current value is deviated from the TWAP value to make sure that the value is not manipulated. Such as spot price and twap price in UniswapV3.\\n```\\n    if (\\n        // `isDeviatingWithBpsCheck()` will revert if `deviationBps` is invalid.\\n        Deviation.isDeviatingWithBpsCheck(\\n            baseInQuotePrice,\\n            baseInQuoteTWAP,\\n            params.maxDeviationBps,\\n            DEVIATION_BASE\\n        )\\n    ) {\\n        revert UniswapV3_PriceMismatch(address(params.pool), baseInQuoteTWAP, baseInQuotePrice);\\n    }\\n```\\n\\nThe issue is isDeviatingWithBpsCheck is not check the deviation of current value to the TWAP but deviation from the bigger value to the smaller value. This leads to an incorrect allowance range for the price, permitting deviations that exceed the acceptable threshold.\\nExample:\\nTWAP price: 1000 Allow deviation: 10%.\\nThe correct deviation calculation will use deviation from the mean. The allow price will be from 900 to 1100 since:\\n|1100 - 1000| / 1000 = 10%\\n|900 - 1000| / 1000 = 10%\\nHowever the current calculation will allow the price from 900 to 1111\\n(1111 - 1000) / 1111 = 10%\\n(1000 - 900) / 1000 = 10%\\nEven though the actual deviation of 1111 to 1000 is |1111 - 1000| / 1000 = 11.11% > 10%

Impact:
This miscalculation allows for greater deviations than intended, increasing the vulnerability to price manipulation and inaccuracies in Oracle price reporting.

Recommended mitigation:
To accurately measure deviation, the isDeviating function should be revised to calculate the deviation based on the mean value: `| spot value - twap value | / twap value`.