…e when writing large data

ResizableFile only extended once even when the data to be written to it was larger than that. For example, if the file is currently 1024 B and we're trying to write 1.5 KiB to it, it would get resized to 2048 B and the write would fail (because 2.5 KiB would be required).

The FileJournal only stores the hash of the votedForNodeId because the size of the stored value has to be constant.
Therefore, FileJournal.votedForNodeId does not return the actual node ID but a proxy object which can be compared against the node ID.

…ed or no file journal is used

- The test was very sensitive to small timing differences.
  This updated version is still sensitive, but it should be much better now. I was unable to trigger any failures even under high load.
- o1 should be a follower after o2's first vote request due to the higher term in o2's message and its timeout not having been triggered again.
- Python 2's math.ceil returns a float instead of an int for whatever reason.

The doTicks approach did not work well because it isn't very accurate and doesn't take into account the time spent outside of the actual ticking.
So this replaces it with a direct loop which compares against the current time to ensure that exactly the right amount of time has elapsed since the creation of the SyncObj.

This test may break again if the time spent inside SyncObj increases greatly; for example, if __init__ takes very long, the start time would not match the corresponding values inside the objects. Each individual tick may also not take too long.