Turtle SimulatedNetwork might be reordering events randomly

SimulatedNetwork code is emulating network delays. In the current implementation, each event is given

```
final Instant deliveryTime = now.plusNanos(
(long) (averageDelayNanos + random.nextGaussian() * standardDeviationDelayNanos));
```

The problem is that there is no guarantee that the next event is delivered after the previous one - the random part can be big at an earlier event and small at a later event, and this will cause events to be reordered.

It is not critical, as the orphan buffer will sort it back, but I think it is unintended. Additionally, for future work, where we will use SimulatedNetwork to exchange messages other than just events, this can be catastrophic (as there is no way things are reordered on TCP stream, some code might rely on the order of messages in some cases, outside of the event use case).

A suggestion would be to fix the code to never reorder events.

Start by locating the SimulatedNetwork implementation referenced in the issue and inspect how deliveryTime is calculated and events are queued. Confirm the behavior with the existing tests or test entry points for Turtle networking; done means simulated messages are not delivered out of order.

Written by the indexing model from the issue text.