(7.4.z) WFCORE-6434 - Managed servers could ignore restart/reload required operations when HC reconnects to the domain

In a domain with a single secondary host with a single managed server: Deploy an application that takes time to start up, which will delay the server process to transition from starting to running Stop and start the managed server. The server process state will be starting until the applications have been deployed. Reload the DC in admin-only mode, the secondary Host Controller will lose the connection with the DC. The managed server is unaffected and continues starting. Change the default value of java.net.preferIPv4Stack system property. Reload the DC in normal mode, the HC will get connected to the DC and will get a fresh copy of the domain model. Since the new copy differs from the java.net.preferIPv4Stack value used by the managed server, the Host Controller will send the restart required management operation to the managed server. The ControlledProcessState state machine will ignore such a transition. The managed server finish deploying the application and managed process state transitions to running The won't be in restart-required, however, it will be using an obsolete value of java.net.preferIPv4Stack instead of the value configured in the DC.