Enable the support of complex IoT data

[schneiti]

Adds functionality for the support of complex sensor data. This includes compound data types and a larger selection of primitive data types.

Main additions (short version):

• Instead of units, each operator (excluding monitoring operators) gets a data model assigned which represents the json structure of the sensor values which will be send via MQTT.
• Modular and configurable visualization charts for complex iot data
• Access to sensor data fields via JsonPath for CEP conditions and visualization settings.
• Utils DocumentReader class for accessing complex data with data model leaf nodes (read and write access to perform automatic data processing, if in future needed)

Steps to bind sensors/actuators to the MBP properly:

As this new version of the MBP adds new required fields to existing database entities it is necessary or at least recommended to drop the local MongoDB collections (at least for the collections: mongoValueLogs, operator, sensor, actuator).

1. Create a new data model which represents the json sensor value MQTT payload and the desired data type mappings.
   
2. Have a look at the generated example mqtt sensor value payload to make sure the data model was defined correctly.
   
3. Connect the data model to the operator. (Make sure that the extraction scripts send sensor values which are in conformity with the data model specification). Examples of such operator scripts (generating random values for test purposes) can be found in
   MBP/resources/adapter-scripts/complex_iot_data_stub/
   
4. Create sensor/actuator instances.

Visualize sensor data

1. In the sensor detail view choose visualization modules. If no module is available this means there is recently no suitable chart for this kind of iot data implemented.
   
2. Click on the settings buttons for a visualization module.
   
3. Choose the data fields you want to visualize
   
4. Click on save.
   

Configure conditions for CEP.

• For each data field which should be accessed for creating IoT conditions, a json path has to be provided via the json path input method next to the condition.
  
• Also multiple filter conditions are now available (connected via AND)
  

Monitoring operators

• Monitoring operators are not affected by the changes and do not need data models, as they are intended to provide simple device metrics.

Closes #17, #531, #530, #529, #528, #500, #501, #508, #509, #510, #511, #515, #514, #607, #621, #619, #620

[schneijan]

Looks great, only found some minor issues to consider before merge.