Fix: quote provider has the enable fot flag awareness

[jsy1218]

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  Big fix

• What is the current behavior? (You can also link to an open issue here)
  There's a bug in the FOT quote and routes calculation path, so that it would cause interface to double quote FOT tax immediately, if we ship Feature: Routing-api support for FOT quote routing-api#362 today.

Let's use BULLET => WETH as an example. Hypothetically interface will issue two requests:

1. BULLET => WETH exact in with enableFeeOnTransferFeeFetching = true. Then it will writes the routes DB with the cached routes with the pool reserves with the buyFeeBps and sellFeeBps . Interface issued this request as part of their QA/testing.
2. Degen uses interface issue a BULLET => WETH exact in quote. Since interface has not enabled to pass in enableFeeOnTransferFeeFetching , routing-api will have useCachedRoutes = true, and read from cached routes with the pool reserves with the buyFeeBps and sellFeeBps . Then in sor, it will calculate the routes and quotes with the buyFeeBps and sellFeeBps .

The problem is in (2), interface has no awareness that the quote and routes are from cached routes, and they have the hardcoded FOT tax logic in prod today https://github.com/Uniswap/interface/blob/main/src/hooks/useSwapTaxes.ts. Since smart-order-router also quoted with FOT tax in quote-provider, this is effectively double FOT taxation in prod, before we enable FOT backend support to 100%. And since cached routes hit rate is over +80%, this bug is considered a blocker before we ship Uniswap/routing-api#362.

• What is the new behavior (if this is a feature change)?
  Quote provider doesn't calculate FOT tax. As such because it also doesn't pass the FOT tax to the outputAmount/inputAmount, the routes returned from routing-api will not include the FOT tax in both token construct as well as the outputAmount/inputAmount.

• Other information: