Update wsts version to 6.0 and use Packet::verify function

[jferrant]

Description

Need the newest wsts version changes for handling <100% participation in DKG
Also required for processing coordinator messages while in the IDLE state which enables DKG to be calculated by all signers simultaneously

Applicable issues

• Part of [Nakamoto] Stacker-Signer binary must handle non-participation #4111
• Part of [stacks-signer] All signers should calculate the DKG key simulateously  #3972

[xoloki]

Lgtm as long as CI (test_stackerdb_dkg specifically) passes

[codecov]

Codecov Report

Attention: 7 lines in your changes are missing coverage. Please review.

Comparison is base (f98656c) 82.89% compared to head (0cfebe3) 82.92%.

Files	Patch %	Lines
stacks-signer/src/runloop.rs	0.00%	7 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #4227      +/-   ##
==========================================
+ Coverage   82.89%   82.92%   +0.03%     
==========================================
  Files         429      429              
  Lines      302932   302864      -68     
==========================================
+ Hits       251109   251154      +45     
+ Misses      51823    51710     -113     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jcnelson]

I don't think the stackerdb tests are running here?

[xoloki]

@jferrant I changed the PR description to specify that this does not close #4111, but it is a part of it. I don't think we should close #4111 until I do that last piece of robustness, i.e. allow partial DkgPrivateShares participation as long as a DKG threshold subset of the DkgPublicShares responders also send DkgPrivateShares. Current wsts 6.0.0 allows partial DkgPublicShares, but then requires that they all send DkgEnd or DKG fails.

[xoloki]

I don't think the stackerdb tests are running here?

I ran test_stackerdb_dkg locally, and it passed. But yeah I don't see an explicit CI action that calls it @jcnelson

[xoloki]

Ok @jcnelson it looks like test_stackerdb_dkg and the other StackerDB tests are part of sbtc-tests.yml, not bitcoin-tests.yml, and they aren't running currently. @wileyj is there some reason the sBTC/StackerDB tests aren't running currently? I know they take a while, but are they flakey in CI?