- The new implementation allows to publish multiple operations
concurrently from different sources

-CollectAgent and Pusher adapted for special handling of event data
-Handful of other fixes and improvements

-add implementation for calieventdatastore
-requires adaption of CA, Pusher to actually store data in it

-CED should go into separate table
-adds header files for required libdcdb extension
-add other sideshow stuff required for new Cassandra table
-actual implementation outstanding

- Also renamed "frequency" column to "interval", can be used for all sensors

Remove  maxConnPerHost and maxConcRequests configuration parameters in Collect Agent as they have been deprecated in Cassandra

- String topics are now used across all of DCDB, up to Cassandra
- As of now, sensor names ALWAYS match MQTT topics
- Users can still define sensor "aliases" via dcdbconfig that point
to the same topics

- Added configuration options to tune the Cassandra driver for
optimal performance
- Added a "debugLog" configuration switch that enables logging of
errors in asynchronous inserts in the Cassandra driver

Refactor JobDataStore functionality for the expected use case

Change CassSchema references to CassSchemaMeta to reflect changes in API change due to cpp-driver update to 2.10.0

Introduced a bit mask for sensor properties in dcdblib and dcdbconfig (e.g., integrable, monotonic,...)

Sets gc_grace_seconds to 600 for dcdb.sensordata upon creation.

Still pending: honor scaling_factor during query().

* Added SensorConfig and DCDBPublicSensor classes as interface for dcdbconfig
* Fixed bugs and tested:
  --> CollectAgent fully working
  --> dcdbconfig fully working

* Bumped Cassandra to 2.1.5
* Bumped cpp-driver to 2.0
* Eliminated cassandraBackend in favor of DCDBConnection

In the future, a DCDBConnection handles the low-level connection
to Cassandra. On top of an established DCDBConnection, you can
create a SensorDataStore object which gives you access to raw
sensor readings.