Automated Dispute Load Test

[eskimor]

One automated test I would like to have some point soon is the following:

1. Dispute lots of valid candidates
2. Also create garbage candidates

Make sure that no block including a garbage candidate gets ever finalized, even under heavy load. This would involve some tracking

Related: Track the order of disputes resolving. Would be good to see, that disputes are resolving in the right order (oldest first).

Both of these should probably be checked in the same test. The ordering does not have to be perfect: If disputes are raised roughly at the same time, then the order in which they resolve is not defined. The ordering is only enforced when dispute participations start to queue up.

In practice this should mean that, assuming nodes are not too much out of sync, it should not happen that a dispute for a candidate on block X + 1 resolves before a dispute for a candidate on block X.

[eskimor]

Implied: The network should not break under heavy load.