Changes in TimeSync object activation

The TimeSync object previously was disabled after system start and had to be actively enabled by the host application at each configuration through EIP_OBJECT_MR_REGISTER_REQ with a certain option flag EIP_OBJECT_MR_REGISTER_OPTION_FLAGS_USE_OBJECT_PROVIDED_BY_STACK. This method is discontinued.

Instead, a new taglist entry TAG_EIP_TIMESYNC_ENABLE_DISABLE defines whether the object will be available after firmware start as a builtin object.
The taglist default is enabled. Unless statically disabled, the timesync object can be dynamically activated/deactivated through the packet API with
EIP_OBJECT_PRM_ENABLE_TIMESYNC_OBJECT, substituting the old method.

This change affects applications that used the TimeSync object in previous firmware versions. Applications that activated the TimeSync object using EIP_OBJECT_MR_REGISTER_REQ have to remove this command and instead must enable the TimeSync object through the new parameter.
Applications that have not used the TimeSync object before are not affected.

Statically disabling of the CIP Sync support allows for the memory being used by another subsystem according to the new EIP resource dimensions tag.