Enable FIRE coordinator for signer

[xoloki]

Is your feature request related to a problem? Please describe.
Currently, we use the original FROST coordinator from wsts. This is a very basic coordinator implementation, it requires that everyone takes part in dkg and sign rounds, and will simply hang if anyone doesn't respond.

Current wsts also has an advanced FIRE coordinator, which will timeout and retry with various strategies for the various operations. It will also return errors if it can no longer make progress, and these errors will specify which signers were responsible for the inability to continue.

Describe the solution you'd like
We should enable the FIRE coordinator for stacks-signer, configure it as desired, and handle the errors it returns.

Describe alternatives you've considered
There are other meta protocols which are even more advanced than FIRE, specifically ROAST which does the same things but operates in parallel with much shorter timeouts. But it would require a significant rewrite of the state machine, and probably stackerdb as well. The FIRE coordinator is already implemented and well tested, and did not require significant alteration of the state machine.

[blockstack-devops]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.