Issue #12167 - Fixed persisting zplsc-b cabled data in Cassandra

[renegelinas]

Fixed several issues that now persists zplsc-b cabled data to the Cassandra database. It now allows the user to use the playback tool or ingest handler to ingest zplsc-b cabled data.
Fixed:
- Added flag to indicate process completion, set by the driver and monitored by the playback tool.
- Fixed transpose method in zplsc_plot to operate on a copy, so data passed to the driver is correct.
- Fixed ingest handler to call zplsc_playback() in playback for zplsc-b data, versus playback()
- Added logging
- Added try/catch where needed
ZPLSC-B data can now be persisted to the zplsc_echgram_data table in Cassandra with errors and the offline zplsc echogram is still being generated properly. However, the data is not able to be potted on the UI and there are Edex warnings when ingesting from the ParticleProcessor:
WARN 2018-10-01 05:03:47,478 [Ingest.instrument_particles-2] ingest: PERF: ParticleProcessor - Message [sensor=CE04OSPS-PC01B-05-ZPLSCB102 module=mi.instrument.kut.ek60.ooicore.driver method=streamed source=/home/asadev/rene/raw-data/rsn_cabled/rsn_data/DVT_Data/pc01b/ZPLSCB102_10.33.10.143/OOI-D20170101-T000000.raw] size threshold exceeded [33620760]
There still needs to be investigation of the message size and not being able to plot on the UI.
The mechanism of getting the data ingested from the playback tool and the ingest handler is fixed.

[danmergens]

We have a weirdness in that we already released and requested a hotfix for 0.6.7. I'll leave it to Tim on how he wants to work that in for the release.