Otter ChaosBot isolate/rejoin resets latency overrides

```
network.setLatencyForAllConnections(targetNode, latencyRange);
network.isolate(targetNode);
[...]
network.rejoin(targetNode);
```

Expectation is that the latency for targetNode is still set to latencyRange, but in the current implementation it is reset to the default.

The easiest way to check it is to set it to a big number (like two seconds) and then see the ping metric for that node in statistics.

Search the ChaosBot implementation for network.setLatencyForAllConnections, network.isolate, and network.rejoin, then trace how the target node's latency is stored and restored. Reproduce the sequence with a large latency, such as two seconds, and verify the node's ping metric in statistics remains elevated after rejoining.

Written by the indexing model from the issue text.