Device is not sending Object Change Indications for TCP/IP attr. 5 on startup

A change in the LWIP component introduced a change in the behavior of the tNetIfStatusChangeJob. Since EipCore V3.9, the LWIP is not changing its IP address to 0 anymore, which in turn leads to no tNetIfStatusChangeJob being triggered.

With the current implementation, the generation of the Object Change Indication during startup is relying on the IP address of the LWIP and in turn the attribute being changed from the value stored in the remanent data to 0.0.0.0 and then back to the IP address configured by the application.

The goal is to re-introduces an Object Change Indication for attribute 5 of the TCP/IP object during startup with the currently configured IP address.