Refactor New event storage/telemetry

[glossyio]

Is your feature request related to a problem? Please describe.
It is hard / manual to add new events / telemetry into the traffic monitor because every new event needs its own on-device database definition (SQLite) and telemetry. I would like a standardized way to create a payload from a new event/telemetry signal to automatically be added to both of these.

Describe the solution you'd like
When a new event framework is created; e.g. adding in completely new sensor and data; create a single payload from that with a defined topic and have it automatically save to a database (SQLite) and sent as telemetry.

There will still be configuration and designations, but modularize/standardize/reuse as much as possible to keep a consistent pattern on saving data to a database and sending telemetry.

This could then enable a standarized back-filling capability with a store-and-forward approach.

Describe alternatives you've considered
There are many ways to accomplish this. Would like to use current Node-RED with local SQLite storage and IoT Hub (ThingsBoard) telemetry endpoints.

Additional context
This would be good to implement with the planned System Metrics and the AQ Sensor milestones.