SolarNode has evolved to support general data transformation services via the GeneralDatumSamplesTransformService API and a separate (older) GeneralDatumSamplesTransformer API. These APIs are used to transform a captured datum into a different form to be then posted to either SolarIn or SolarFlux. Both streams actually have similar code to execute the transformations, but the overlap is a bit confusing for users, especially for things like the VirtualMeterSamplesTransformer.

This ticket is to come up with a better, more consistent "transform pipeline" that can be configured. A "transform pipeline" would be an ordered list of GeneralDatumSamplesTransformService implementations. The pipelines themselves can be Identifiable and then referenced by the SolarIn and SolarFlux upload services. In the case of SolarIn, care must be taken so that the transform pipeline works for both SolarIn/MQTT and SolarIn/HTTP.