Do not attempt to treat miner as a coordinator when updating DKG

[jferrant]

This only really matters for epoch 2.5. If this was to happen in epoch 3.0 the chain would be halted.

[codecov]

Codecov Report

Attention: Patch coverage is 73.91304% with 12 lines in your changes are missing coverage. Please review.

Project coverage is 82.81%. Comparing base (929a9b8) to head (4b26a2c).

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #4591      +/-   ##
==========================================
+ Coverage   77.90%   82.81%   +4.90%     
==========================================
  Files         470      470              
  Lines      332714   332704      -10     
  Branches      317      317              
==========================================
+ Hits       259201   275518   +16317     
+ Misses      73505    57178   -16327     
  Partials        8        8              

Files	Coverage Δ
stacks-signer/src/main.rs	36.00% <ø> (+20.92%)	⬆️
stacks-signer/src/runloop.rs	91.08% <100.00%> (-1.28%)	⬇️
stacks-signer/src/signerdb.rs	90.98% <0.00%> (ø)
stacks-signer/src/coordinator.rs	78.16% <0.00%> (+23.06%)	⬆️
stacks-signer/src/signer.rs	72.81% <82.50%> (-0.79%)	⬇️

... and 186 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 929a9b8...4b26a2c. Read the comment docs.

[kantai]

This looks okay, but I think that this should be encapsulated in the Signer::get_coordinator() function.

[jcnelson]

LGTM

[obycode]

lgtm

[jcnelson]

LGTM; just minor things

[obycode]

LGTM just one accidental repeated log line.