Daemon Common - message implementation

- completed the implementation of a client/server interface for the controller/daemon communications
--- interface is fully threaded with mutex access to the queues
--- each connecting controller operates in its own thread
--- the server interface uses a dedicated thread for accepting new connections
--- all messages are wrapped by a message header that provides:
----- some versioning capability if required
----- length specifications of the entire message and just the message data
----- message types if required
Bug Fix: Don't return the header data, just the message

- Updated to only return the message instead of the message+header.
--- header is only for the comms benefit and doesn't mean anything at upper layers