SimOpt Communication refactoring

[abeham]

A number of recent developments has made refactoring the communication branch worthwile:

1. There exist good libraries for converting data to and from e.g. JSON both on C# and Java which facilitates interlanguage communication. Even the new serialization in HeuristicLab 3.3 would allow for a JSON backend.
2. The whole statemachine idea was nice, but hardly ever practical or useful. Google's own take on such an interface (​protocol buffers) doesn't need a state machine. A simple set of messages should do it in our cases too.
3. I have more upcoming use for this, so I'd like more comfortable configuration and handling