Send Signer results over a channel

[xoloki]

Description

Right now the only way to find out what a Signer has done is to stop it and get the cached results.

Add another channel which lets Signer send results as they come in.

Applicable issues

• Closes [Signer] The run_one_pass on exit should return a vector of OperationResults rather than a Point #3916

Additional info (benefits, drawbacks, caveats)

Checklist

• Test coverage for new or modified code paths
• Changelog is updated
• Required documentation changes (e.g., docs/rpc/openapi.yaml and rpc-endpoints.md for v2 endpoints, event-dispatcher.md for new events)
• New clarity functions have corresponding PR in clarity-benchmarking repo
• New integration test(s) added to bitcoin-tests.yml

[codecov]

Codecov Report

Merging #3923 (32e8dab) into feat/stacks-signer (99c1218) will decrease coverage by 0.01%.
Report is 1 commits behind head on feat/stacks-signer.
The diff coverage is 0.00%.

@@                  Coverage Diff                   @@
##           feat/stacks-signer    #3923      +/-   ##
======================================================
- Coverage                0.16%    0.16%   -0.01%     
======================================================
  Files                     339      339              
  Lines                  290170   290260      +90     
======================================================
  Hits                      469      469              
- Misses                 289701   289791      +90     

Files Changed	Coverage Δ
libsigner/src/runloop.rs	0.00% <0.00%> (ø)
libsigner/src/tests/mod.rs	0.00% <0.00%> (ø)
stacks-signer/src/crypto/frost.rs	0.00% <0.00%> (ø)
stacks-signer/src/crypto/mod.rs	0.00% <ø> (ø)
stacks-signer/src/main.rs	0.00% <0.00%> (ø)
stacks-signer/src/runloop.rs	0.00% <0.00%> (ø)
testnet/stacks-node/src/tests/signer.rs	0.00% <0.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[jferrant]

I updated the state machine substantially and fixed the test to actually tear down the signers at the end. My initial check on the meaty portion (following node and signer setup), it takes ~15 seconds to run DKG and Sign a message.

[xoloki]

I fixed the build so we don't expect any additional types to impl Clone, and rebased on the merged signer-first PR. This PR should be ready to go now.

[jcnelson]

LGTM. Thanks for addressing my comments!