co⚡e: Sparkplug™ MQTT edge

Upgraded lib to v0.0.0.20 and adjusted the calls to match the refactored lib

V0.0.021 of library as by first suggestions of I-Campbell;
* Functions FindChanges and listComposer moved to SparkPlugB as methods.
* FOR index := LOWER_BOUND ... TO UPPER_BOUND.. DO
* CheckBounds() added for checking array sizes => TODO check array sizes(!)
* Added method SparkPlugB.PublishNodeData()

Fresh copy from trunk

deleted /unittest for a fresh copy from trunk

Commit of binary unittest.project to trunk

Corrected the testproject for further usage

synced changes from trunk library into branches/i-campbell

binary of unittest.project

Added some test skeletons to FB_EoN_Node (were found in r293)

Commit of binary unittest.project to trunk

Commit of corrected unittest as startingpoint for 'MVP milestone'

Corrected unittest for 0.0.0.20;
Now ready for Edge of Network Node tests etc.

Commit of binary library to trunk

Updated trunk to UNTESTED 0.0.0.20 version of Aliazzz Branch

Draft for FB_EoN finnished.
Needs testing, debugging, sunshine and water.

FB_Edge_Of_Network_Node;
* Added ListComposer Function
* Reworked Initialise to compose _ListOfAllMetrics

SimpleTypes expanded with;
* 'notify' getter,
* 'Value' getter changed to only accept a value on difference + triggers 'notifier'

commit of binary unittest.project

Merging unit test from /branches/i-campbell

There were some unit tests which shared resources. separating these resources solved the final test [#45]
I also noticed at one point, there was a Direct copy of a list:-
MetricPool : SparkplugB.List;
GVL.AllMetricsList : SparkplugB.List;
MetricPool := GVL.AllMetricsList;
This probably caused the headaches in [#47]
Maybe there is a trick to prevent copying lists like that?

branch trunk library to branches/i-campbell/

branching unittest to /branches/i-campbell/

we don't need no branch stagnation

Updated Trunk Unittest With Aliazzz Personal Branch

Updated Trunk Unittest With Aliazzz Personal Branch