Changed Time Sync object activation

The CIP Time Sync object will be reworked as follows:

• Dynamic registration/creation of the object will be abandoned (packet EIP_OBJECT_MR_REGISTER_REQ).
• Instead, a taglist entry will define whether object is registered at the EtherNet/IP-Core during power on sequence.
• The host application can set a parameter to dynamically unregister/re-register the Time Sync object during the next firmware reset, unless it has been disabled in the taglist.

This has multiple advantages:

• TimeSync's remanent data issue for SetConfig use cases should resolve.
• All PTP init code can go to the XIP, freeing up considerable heap space on netX52.
• Avoiding to dynamically malloc and free the object and PTP resources will reduce memory fragmentation and chances of runtime failure.

Drawbacks:

• This is an incompatible change, since it deprecates the TimeSync MR-register feature and substitutes it with a stack parameter. Since we probably will have the TimeSync enabled as the taglist default, a host application which seeks not to implement the TimeSync object (the majority of applications), has to actively set the stack parameter to disable it through either the packet interface, the taglist, or both.