Add an admin local E2E test to test TSS migration

[lumtis]

Describe the Issue
Add a local E2E test that can do the following:

• Start the local environment and send cctxs normally
• Stop cctxs
• Perform a TSS migration. There are several options we can consider implementing:
  • New observer added
  • Observer removed
  • Observer updated
• Check the TSS can migrate funds
• New cctxs can be created

Tasks

Preview Give feedback

1. Automatically restart clients when a new keygen is set #2370
   zetaclient +1
2. Add query for tss fund migrator #2371
   +0
3. Test TSS migration #2441
   +0
4. Fix double minting of ZRC20 tokens #2442
   zetacore +1
5. Add Connector and ERC20 custody contract update for TSS migration test #2443
   E2E +1
6. Add option to rerun entire test suite after TSS migration #2444
   E2E +1
7. Move restart logic from supervisor into the zetaclient directly #2455
   zetaclient +1
8. Improve validations for outbound nonces on zetaclient #2487
   zetaclient +1
9. Use retry package for queries on zetaclient #2492
   zetaclient +1

[kingpinXD]

Add, Remove observer is a separate functionality from TSS migration and should be tested separately .
It would make sense to create a e2e test first which does the following

• Sets a new keygen
• Restarts zeta-clients so that they pick up the new keygen and generate TSS
• Migrate TSS funds
• Update TSS address
• Test cross-chain transactions

[lumtis]

Add, Remove observer is a separate functionality from TSS migration and should be tested separately .
It would make sense to create a e2e test first which does the following

• Sets a new keygen
• Restarts zeta-clients so that they pick up the new keygen and generate TSS
• Migrate TSS funds
• Update TSS address
• Test cross-chain transactions

This can be a first step but why not putting everything under the same test in the end?