"Failed to signal ready to sign" - Prison extension

[adamPetho]

This PR is made to address this https://github.com/zkSNACKs/WalletWasabi/pull/11115/files#r1294451295
and to push forward #11115 PR.

This PR adds a new method to Prison called FailedToSignalReadyToSign.
On master this method is not yet used. It will be used in #11115 AFAIK.

FailedToSignalReadyToSign has the same penalty factor values as FailedToSign. Please let me know if this should be different.

[Szpoti]

ACK.
Code LGTM

[lontivero]

Missing parts:

• You have to serialize and deserialize the new type of disruption; otherwise they will not be persisted.
• Update unit tests for this new type of disruption.

[adamPetho]

@lontivero There is a bit more complex unit test called BanningTime. I have a hard time updating it, because I'm not sure how hard do we want to punish this misbehavior.
Is it OK to handle this misbehavior as the FailedToSign? Or should it be a bit lesser than FailedToSign?

[lontivero]

Is it OK to handle this misbehavior as the FailedToSign? Or should it be a bit lesser than FailedToSign?

I think it is just a bit less than FailedToSign because it wastes less time from everybody else but don't worry about that, you can make it the same as FailedToSing for the test because in the end these factors have to be tweaked in production.