Peter M. Groen / FlashMQ

The file IO is blocking, so we don't want that in our thread loops.

This avoids changing which thread runs the code.

Also let auth_plugin_serialize_init affect cleanup serialization.

It was a mistake that it ran inside the timer thread, which came to
light by asserting the thread local authentication pointer (see a few
commits ago).

There were bugs in which authentication object was used when, causing
threadings bugs. Instead of getting from the 'sender', we can just store
a thread local pointer.

Files are simple serialized bytes prefaced by lengths. File is hashed to
verify integrity. This was also a good way preventing unexpected errors
when trying to crash the parser by having it load a different file.

This change includes some refactoring that was necessary:

- It 'fixes' looking at the wrong thread's authentiction. This is still
  wrong though. It will be fixed by a thread local pointer in the next
  commit.
- Deadlocks with yourself are handled in rwlockguard.
- QoSPacketQueue is now a class.
- Probably other tweaks.

This performs a whole lot better.

Also include a few stats.

Encrypted version only.

My IDE didn't understand them for finding symbols, apparently.

Having threads creates instability for the fuzzer, and we don't need
them.

This also adds configuration options for choosing what address to bind
to.

Probably I also need a flag to fake already being upgraded, because
otherwise we never get passed the complicated websocket handshake.

This can be called by a fuzzer like afl-fuzz.