User stake migration from non-upgradable staking pool to the upgradable staking pool

[janewang]

Story

Facilitate the NEAR stake migration from poolv1.near to pool.near.

Acceptance Criteria

• [ ] The user is alerted that the need to migrate their stake from old pool to new pool
• [ ] To avoid all stake migrating at the same time, the user migration is organized into batches
• [ ] The user can one-click unstake from the old staking pool
• [ ] The user will alerted when the stake is ready for withdraw
• [ ] The user can one-click restake to the new staking pool
• [ ] Mobile tested
• [ ] If a validator doesn't set up a new staking pool, we will alert the user that they are staking to a legacy pool and to move their stake.

Unhappy Path

• The user unstake and then cannot restake to a corresponding pool
• All users unstake at the same time
• The user forgets to restake

NOTES

• The expectation is that the validator will use the same name for the old pool :: new pool mapping (unless they reach out to use and specify otherwise)
• Coordinate with delegation for stake by NF
• Pending contract audit (no timeline at this point)

[stefanopepe]

@corwinharrell This issue is critical for the protocol at large, as the entire staking will have to move to a new pool (that will be upgradable, so the problem will be solved for good). The timeline is not urgent, but it's extremely important and must be ready when the new staking pool completed the security audit