co⚡e: Sparkplug™ MQTT edge

update of branch

Version 1.1.0.13
Fixed the Rebirth publish issue for a connected device after the Server Node requests an EoN Rebirth
Fixed improved readability and control over the state entry, exit and continuous parts in EoN/Device
Fixed stable Device state

After a fierce fight with the code, we managed to get it working! Thx Ian
v1.1.0.11 features a working Device with a working DBIRTH /DDATA publish

Todo:
1) Refine the mechanism to allow for a DBIRTH after a Rebirth has been issued;
Hint: check the command chain and its feedback
_ItfCurDevice.NotifyBIRTHPublish := _ItfCurDevice.NotifyBIRTHPublish + 1;

2) Test/ check /refine to allow for more then 2 devices to publish MQTT wise

3) Implement DDEATH

v1.1.0.10 Device DBIRTH and DDATA working with stable seqnums.

> Encoder init separated from .addSeq
> Some EoN methods moved to Functions
> EoN notifies Device(s) when to Publish
> GC_SparkplugB Global Constants list
> Improved EoN state machine

TODO;
DDEATH
NCMD
DCMD

v1.1.0.10 Device DBIRTH and DDATA working with stable seqnums.

> Encoder init separated from .addSeq
> Some EoN methods moved to Functions
> EoN notifies Device(s) when to Publish
> GC_SparkplugB Global Constants list
> Improved EoN state machine

TODO;
DDEATH
NCMD
DCMD

v1.1.0.5 Device ith may tweaks but still no working SeqNum for DDATA...

> Encoder init separated from .addSeq (!)
> Some EoN methods moved to Functions
> EoN notifies Device when to Publish
> GC_SparkplugB Global Constants list

Branch of Trunk

Device V1.1.0.1

TODO
* Check publishing DBIRTH Topic SeqNum (should be working)
* Check publish DDATA SeqNum (triggers REBIRTH, not correct yet)
* Publish DDEATH of a Device when occurs