Missed in 4df3c4e1.

Since lib.protocol has been rewritten to be semantic-oriented and
duplicates a lot less code, this test is just bloated (testing the same
code over and over) and a maintenance burden.

It is intended to raise even when running in optimised mode. The intent of
that change was to allow interpreter to detect the last elif is not
expected to be needed (although it is not known to make such deductions
currently). If only python had a deeper "enum" notion...
This (very) partially reverts f32e9120.

Also, log node's final UUID, not the one it advertised.

Also, tweak condition order to accelerate the most likely case: it is
expected to have more clients than storage nodes, more storage nodes than
master nodes, more master nodes than admin nodes and no unknown node type.

In turn, stop returning uuid from identifyNode.

We are testing values coming from an Enum, and we are testing all existing
values.

The main goal of this patch is to keep all DEBUG logs and packet logger enabled
without exploding disk usage.
This is done by keeping the last 16 MB (by default) of debugging information in
a RAM buffer, and to emit it to an SQLite DB upon RTMIN signal or in case of
warning and more severe log.

Implementation is also cleaned up for better integration within a framework
or if run standalone. NEO logger is now a direct child of root handler.
Only warnings and more severe logs are forwarded to root handler.

A new script 'neolog' is added to pretty-print the contents of the SQLite log.

In unit tests, logging events are not buffered but emitted immediately.
When a test passes, payloads of all exchanged packets are discarded to reduce
disk usage on test bots.

This slows down performance tests by about 15 % because even if nothing is
written to disk, debug and packet log records are now always rendered.

sed is your friend.
Also, factorise setUp definition.
Also, use "super" to call methods on superclasses.

Preserve AskPrimary/AnswerPrimary for neoctl/neoadmin exchange only.
Fixes several race conditions during election.

Otherwise, in the case of an unexpected packet, an incorrect message id
would be used.
Also, refuse setting a None peer_id on connection.