CFG Migration: Legacy CFG to new CFG

[0x4Graham]

To support the legacy CFG (Centrifuge CFG) migration process, we need to implement the migration flow user interface as shown in the images attached. This includes creating the migration interface, confirmation popup, and success notification. This ticket covers the front-end implementation only; smart contract integration will be handled in a separate ticket.

Designs: https://www.figma.com/design/ng7qdNcSCXSDA6ZUdWIs6u/Pool-Overview%2F-Pool-Detail?node-id=5977-25055&t=ujfWFB0DtyOxeT4U-1

The main difference between this ticket and the WCFG migration is the addition of an Ethereum address that the user needs to provide. This step involves some complexity to ensure that the user is in control of the wallet, so that no mistakes can be made and then migrated CFG cannot be lost.

1. UI for the Legacy CFG Migration:

2. When user connect's their Ethereum wallet here, we need to get them to sign a message confirming ownership of their wallet. The message they sign should say the following:
   "I hereby confirm I am in control of the wallet that will be receiving the migrated CFG".
   -- What do we do about safe's here.

On succesfull signing of the message, we store the wallet address in the field. And show the verified wallet button.

3. Clicking migrate, provides a summary page of what the suer will confirm

4. Begin Migration. Let's store the status of a migration somewhere so that if the users refreshes they don't lose this and then panic.

5. Success page