feature: migration v2-v3 avalanche and Polygon [skip cypress]

[satanworker]

General changes

Dedicated page with logic to handle migration from AAVE v2 to v3.
In nutshell, migrating from v2 to v3 positions requires, to set current market to v2, while simultaneously fetching data for v3.
Selecting positions from v2 should dynamically change health factor and display both before and after migration HF for both v2 and v3.

When user selects multiple assets to migrate, supply asset amount should be slightly increased to allow migrating the whole position, or the balance would grow during approving and transaction execution and method would fail as HF will fell below 1, with no supply and a little bit of debt.

In order to properly do that, changes in the whole transaction flow on the aave interface required. More specifically, changes to how useTransactionHandler is working.
On any modal opens in the app after small delay, transactions are filtered into approval and actions by transaction type.
If approval state is not empty, that means we need to approve action first with permit if available after with on chain approval.

Currently, AAVE interface assumes that each Action in the app will have single approve or single permit and single following transaction. Although it worked great for most parts, specifically for migration it didn't work, since migrating multiple positions would require approving/signing permit for each supply asset.

Also, it's the first pr with new changes done in zustand completely, which also changed a bit the flow working with Actions component, as mentioned in this discussion, we want to migrate from idea of dedicated actions component anyway. It also showcases how easy it is to nest multiple non-destructive data manipulation in selectors. i.e. increasing amount, filtering for non-empty states, etc. Which is the bulk of the logic in the app.

Isolation mode

When user has 0 collateral on v3, the order of supply assets will define the isolation mode, if isolated supply is supplied on v2.
Supply USDT as collateral to empty balance on v3, will automatically enable it as collateral and activate isolation mode, therefore supplying any other collateral will be ignored.
To make it easier for user to understand enabled as collateral toggles are presented.
The logic is following, if only isolated supplies are selected, the last one will be selected as collateral and therefore migrated first.
if any non-isolated supply is available, non-isolated supplies will be selected as collateral. Non-isolated supplies will be migrated first. Since it’s way harder to migrate from isolated supply to non-isolated one.
It’s still possible though to enable isolated supply manually and user choice will be respected.
The situation gets more complicated with non-empty balance on v3, which is not enabled as collateral.
In that case supplied assets on v3 can not be toggled as collateral, but the rest of the assets will still follow the same rules of the first migrated supply will trigger isolation mode. For example

In this example, user has DAI disabled as collateral on v3 and that’s why it’s disabled for usage as collateral on migration page.
But MATIC or USDT can be triggered as collateral and therefore define the isolation mode

Balancer will be enabled/disabled for migration based on isolation mode dynamically

Developer notes

Since v2-v3 migrator is not deployed, use this RPC for testing

localStorage.setItem('forkEnabled', 'true');
localStorage.setItem('forkBaseChainId', 137);
localStorage.setItem('forkNetworkId', 137);
localStorage.setItem("forkRPCUrl", "https://rpc.tenderly.co/fork/f1fcc2cc-c0ca-45c6-9f8b-92a4ab4b053f");

Be careful fork chain is equal to real chain ID on purpose, in order to test permits, both fork and base chain id required to be the same

contract helpers version is set to deployed of this PR
aave/aave-utilities#459 once we merge it to main will change to bumped version

Demo

(top UI was changed a bit)

CleanShot.2022-12-06.at.18.54.07.1.mp4

To discuss

[ ] Discuss how to dynamically change market names based on chain ID after migration deployment

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[github-actions]

❌ CI run has failed!
Please see logs at https://github.com/aave/interface/actions/runs/4014542267'

[github-actions]

📦 Next.js Bundle Analysis

This analysis was generated by the next.js bundle analysis action 🤖

⚠️ Global Bundle Size Increased

Page	Size (compressed)
global	489.86 KB (🟡 +7.66 KB)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

New Page Added

The following page was added to the bundle from the code in this PR:

Page	Size (compressed)	First Load
/v3-migration	28.14 KB	518 KB

Eleven Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
/	41.49 KB (🟡 +554 B)	531.36 KB
/404	6.35 KB (🟡 +112 B)	496.21 KB
/500	6.79 KB (🟡 +139 B)	496.65 KB
/faucet	22.3 KB (🟡 +154 B)	512.16 KB
/governance	62.53 KB (🟡 +123 B)	552.39 KB
/governance/ipfs-preview	107.74 KB (🟡 +125 B)	597.61 KB
/governance/proposal	107.9 KB (🟡 +125 B)	597.76 KB
/governance/proposal/[proposalId]	62.6 KB (🟡 +125 B)	552.46 KB
/markets	16.07 KB (🟡 +174 B)	505.93 KB
/reserve-overview	64.76 KB (🟡 +157 B)	554.62 KB
/staking	20.55 KB (🟡 +135 B)	510.41 KB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

[github-actions]

• Ipfs hash: bafybeiarcp7rugp3nlx6zbxb7q6znjdpgcnidxigibfmj4etzeld2enf5a
• Ipfs preview link: https://bafybeiarcp7rugp3nlx6zbxb7q6znjdpgcnidxigibfmj4etzeld2enf5a.ipfs.cf-ipfs.com/

[github-actions]

❌ CI run has failed!
Please see logs at https://github.com/aave/interface/actions/runs/4015095477'