Move all message deserialization to LibCommProcessor

Demonstrates how to move the Camel-specific message handling to the base class. 

Each individual processor only needs to implement the ```processMessage()``` function, defined in the ```IProcessor``` interface.

Something yet to be done:

* The ```ModsProcessor``` class currently assumes it's operating on rawXML files, rather than ```LibCommMessages```. That needs to change before it can be adapted to this model.