Split the dynamic_graph_manager in two

[MaximilienNaveau]

Problem

Related to https://github.com/machines-in-motion/dynamic_graph_manager/issues/5 and https://github.com/machines-in-motion/dynamic_graph_manager/issues/4 we need to split the main class.

Potential Solution

• Create a DynamicGraphProcess class and a HardwareCommunicationProcess class.
• Create python bindings for both in order to have them living a python terminal (help the learning people to manage their code).

[jviereck]

How about ControlProcess and HardwareProcess?