This fixes a regression in commit 83fe64bf
when ttrans has several rows to the same data_id.

- Server connections can now be in 'connecting' state.
- connectionAccepted event (which has never been used so far) is merged into
  connectionCompleted.

This is a workaround to fix holes if replication is interrupted after new data
is committed.

AssertionError are certainly more severe that any other exception
(including OperationFailure) because the process is in an unknown state.

This could have been useful in testStorageFailureDuringTpcFinish:
close() could not be called from answerTransactionFinished because it
deadlocked while trying to send notifications.

The test was relying on fact on the fact that 'c.abort()' caused an assertion
failure, which closed the connection and then raised OperationFailure.
Actually, I wanted to close the connection on master, but it's clearer this way.

Previous code relied on the fact that the exception target is kept past
the end of the except clause. 2to3 is not smart enough to detect that.

Without this change, a different OperationalError exception would be
ignored because there's already a local variable of the same name.

This was forgotten when this table was introduced in
commit f9a8500d

If needed, sortStorageList can be extended in the
future to support a 'readable' parameter.

We can never receive several answers from the same node.

testVerification is dropped for the same reason as for testEvent and most of
testConnection, since there is much incoming changes for verification.

- Last known TID was not updated when recovering a transaction.
- Missing OIDs were ignored, which caused partial transactions to be committed
  instead of being deleted.

The previous SQL query caused a full table scan of the 'trans' table at startup.

I used git-diff for each file and concatenated the result to preverse the order.

This fixes invalid next_serial entries in cache,
and the following error for values not in cache:

  Traceback (most recent call last):
    File "ZODB/Connection.py", line 856, in setstate
      self._setstate(obj)
    File "ZODB/Connection.py", line 894, in _setstate
      self._load_before_or_conflict(obj)
    File "ZODB/Connection.py", line 922, in _load_before_or_conflict
      if not self._setstate_noncurrent(obj):
    File "ZODB/Connection.py", line 945, in _setstate_noncurrent
      assert end is not None
  AssertionError

When run with MySQL, testBasicStore (neo.tests.threaded.test.Test) was slow
and generated log exceeded 29MB.

This increases the number of rows to check per AskCheck*Range packets.

And document 3 bugs found by running many times testBackupNodeLost. About the
tic() issue, I had a case where the test exited instead of looping forever after
the storage crash.

Before, it was only done for 'logfile'.