Unify the threshold type used in all algorithms #348
Description
Background
Historically we've used the term threshold inconsistently, sometimes referring to the max number of malicious parties (max malicious) and sometimes referring to the amount of parties needed to reconstruct the private key (reconstruction bound).
We've already introduced strong types in the code for this, but some algorithms takes a reconstruction bound as input and some takes max malicious as input.
It would be nice to have all algorithms use the same threshold type.
User Story
As a crypto developer, I'd like us to use consistent threshold terms to make it easier to work with different algorithms with minimal context-switching overhead.
Acceptance Criteria
We consistently use either max malicious or the reconstruction bound as input to all signing and DKG algorithms.
Resources & Additional Notes
Note: We want to update the MPC nodes to use the strong types before changing the interface, to ensure this doesn't break the nodes in surprising ways.