feat: permit2 allowance flow for zrx swaps

[woodenfurniture]

Description

Breaks token allowance approval UI components into reusable ones in prep for permit2 UI flow.

Notable non-permit2 changes:

• Adds default "exact" allowance state per conversation with product (previously this was only the case for LiFi trades).
• Copy for allowance reset is now "allowance reset", not "approval reset"
• Copy for allowance approval is not "allowance approval", not "approval"
• Code renaming to correspond to the above
• Combine allowance reset and allowance approval steps into a single allowance step component
• Migrates 0x swapper to use api proxy
• UI will persistently display all approval related TX hashes (e.g both the allowance reset and allowance approval), with better naming

Permit2 changes:

• Fully implements Permit2 flow, which consists of an initial unlimited allowance approval (toggle will be hidden) followed by a signature
• If the initial approval was already processed for the sell token, only a signature is required
• USDT allowance reset never appears for Permit2 because only unlimited allowance is presented when initially approving. If a user gets into a state they need to reset their allowance, they will have to use https://app.unrekt.net/
• A feature toggle to disable the Permit2 version of the 0x swapper has been included so we can fall back to the v1 API if we have any issues. Due to the surface area of the change, no feature toggle exists for the UI and state changes so extra care is required to ensure we roll this out without issues.

TODO:

• Beard oil
• ETH -> ERC20 broken
• insufficient for fees
• triple check zrx still works with flag off
• triple check zrx v2 api proxy endpoints are deployed to prod

Issue (if applicable)

progresses #7648

Risk

High Risk PRs Require 2 approvals

This is a high risk change because it heavily modifies the state management of trades and completely rewrites the UI associated with allowance approvals.

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

All trades, especially those with token allowance approvals. Due to the surface area of the change, no feature toggle exists for the UI and state changes so extra care is required to ensure we roll this out without issues.

Testing

General

• trades on all chains

non 0x trades

• without allowance approvals
• trades with allowance approvals
• trades with USDT allowance reset and approval
• multi-hop trades

0x trades

• with REACT_APP_FEATURE_ZRX_PERMIT2 feature flag enabled

  • without allowance approvals
  • trades with allowance approvals
  • trades with USDT allowance reset and approval

• with REACT_APP_FEATURE_ZRX_PERMIT2 feature flag disabled

  • trades with initial Permit2 allowance approval + sign
  • trades with Permit2 sign only (i.e allowance previously approved)

Engineering

Operations

There is a feature flag in this PR but its used only as a fallback if we need to disable permit2 trades for any reason. The changes made in this PR still affect the app majorly regardless of whether the flag is enabled.

Screenshots (if applicable)

non-0x trades

• without allowance approvals
  https://jam.dev/c/27122198-3e0e-4669-84a9-37bdcb76fc52
• trades with allowance approvals
  https://jam.dev/c/0aadbb0a-681a-400d-86bb-80bc6a9e36e5
• trades with USDT allowance reset and approval
  https://jam.dev/c/671e6347-c888-4b11-95ab-0275728a1729

0x trades

• trades with initial Permit2 allowance approval + sign
  https://jam.dev/c/7c1535c7-1966-4ed0-807d-40ef332b46f6
• trades with Permit2 sign only (i.e allowance previously approved)
  https://jam.dev/c/d6d8af5d-0e6d-486d-90bf-fcb4e3976bf5

[gomesalexandre]

First very very high-level pass to get familiar with this - untested at runtime just yet and allowance hooks still not reviewed, but looks solid from this first read!
Some comments re: generalization and naming mostly, though nothing obviously stands out as wrong here.

[gomesalexandre]

First runtime pass with permit2 flag enabled

• RUNE -> AVAX (THOR) - note Tx history is sad but irrelevant to this PR, got a Zerion notification that fundus were received
  https://jam.dev/c/96cc06bb-74fd-4257-9bed-e694e20d4aa2
• XDAI -> FOX (Li.Fi)
  https://jam.dev/c/af077d67-8da7-4513-8206-f1970109de02
• FOX -> XDAI (CoW, no allowance granted)
  https://jam.dev/c/34b13a10-c595-4f45-905c-9701b73571a7
• FOX -> XDAI (CoW, allowance granted)
  https://jam.dev/c/4ff9213d-c873-4da6-beb2-d046be67fd0b
• Shitcoin -> ETH bridge (Li.Fi, no allowance granted)
  https://jam.dev/c/5b65b4af-3d15-4bb8-8320-cb1645b0774e
• FOX -> ETH (0x) quote 🚫
  Getting this error response back from ZRX

- USDT.ARB -> ETH.ARB (0x) quote 🚫 Same here:

Also tested with the flag off:

• USDT.AVA -> AVA.AVA (0x, no approval granted)
  https://jam.dev/c/8089bdbc-40d3-4df5-96b5-ffdd763162e3
• USDT.AVA -> AVA.AVA (0x, approval granted)
  https://jam.dev/c/700cb7f9-bb00-4ecb-b3ca-bc00ac057312
• ETH -> USDT (Li.Fi)
  https://jam.dev/c/3b55d215-c082-4574-9e93-297caf73d6d0

Unable to test more USDT flow re: unlimited, 0, and approval reset flows for the time being because of low fundus

[gomesalexandre]

Tested locally after local origin/develop rebase and LGTM for all tested flows, minus one spotted issue re: permit2 contract approval being prompted (with the flag on) when there is enough allowance, and there shouldn't be any new allowance Tx, hence no permit2 contract approval nor actual allowance Tx/permit2 EIP712 message signed and broadcasted.

See testing in https://gist.github.com/gomesalexandre/6c0b209f940b64a09d726c53ad7f7527

[0xApotheosis]

Code is looking solid, permit flow is solid.

I noticed one blocking regression whilst testing - on this branch we only seem able to get 0x quotes for the Ethereum chain. See screenshots below (left is this branch, right is production):

Nitpick: the tooltip being after a : is odd:

[gomesalexandre]

Retested locally as a last paranoia pass after last changes and confirmed we're looking good at runtime:

https://gist.github.com/gomesalexandre/ab10310c3aff40bd37c00fb15c3ed4da

One q: re price or quote logic for permit2, but otherwise looks sane to land :fridaydog:

[0xApotheosis]

My nitpick feedback was addressed, and I'm putting the quote issues I had down to dev endpoint shenanigans.

gm