A few enhancement to chain signature integration testing

[ailisp]

There is a few places we can enhance current chain signature testing without a lot of work:

• Create a main function so developer can spin up a network of nodes locally, similar to fastauth integration test has. More over, this main function can:
  • spin up only dependency services but not mpc-recovery-node itself
  • print out command to spin up individual mpc-recovery-nodes
  • spin up both services and given number of nodes

An typical use case for this main function would be spin up local nodes and do manual testing or debug certain issue. Once the test is working it can be written down as a with_multichain_nodes test

• A setup (indexer, mock s3) maybe reused for multiple integration tests
• Some test is a strict subset of the other tests, we may want to merge them: only merge strict subset, not merge all tests in to one
• Logs from different nodes are mixed together, it would be very helpful to seperate them to different log files
• Dependent docker services can fail during running result in test fails, we should properly handle these failures: rare when test in single thread, not a problem now

[volovyks]

Sounds reasonable, let's prioritize and start working on this.

[ChaoticTempest]

This is a great way to debug through each services individually too. Sounds like a great addition