Switching to managed socket

When deriving from the socket class, implicitly all its public methods
are exposed. But we want to have control over the API, thus we
encapsulate the socket and offer only relevant information.

The peer socket now finds out about the MTU of the NICs on the host.
This will determine the buffersize for the SAEA objects, since we can
not receive messages that have a bigger size then that.

Exposing exceptions is avoided by catching them all in the required
places.

NET-4, NET-9
Additional information for tests

I added some messages with information about the socket initialization.
Get the PeerSocket working

With this implementation state the PeerSocket is able to accept
datagrams asynchronously. It is working with 10 preallocated SAEA
objects that are reused and emits a new message event when new data
comes in.

NET-4