[BUG] Decided Event for non existing value.

[SamHSmith]

Quite frequently we receive a ProcessSyncedValue for a certain value. Without direct previous network communication! ReceivedProposalPart must have been called far earlier. After reporting the Synced Value as Valid we receive a Decided event for a completely different proposal. A proposal our node has not seen before. I think malachite is getting confused internally and associating a commit certificate with the wrong proposal.

[cason]

We are aware that the logging for the synchronization protocol is not ideal and we are working to improve it.

Is there a setup where we can reproduce the reported scenario?