sometimes ApplicationReady not send in Release-Alarm sequence handling misconfigured SharedDevice

If two IO Controllers want to use the exact same submodule, the first one to establish the connection gets ownership and can use the submodule. The second one is informed hw can not use the submodule. If now the owning IO Controller aborts the connection, the second IO Controller is informed with a Release Alarm that he is now the new owner of the submodule and can use it.

The Release Alarm is handled just like a PlugSubmodule. The IO Controller sends parameters and ParameterEnd to the Device. Afterwards the Device sends ApplicationReady and afterwards the alarm is finally confirmed by IO Controller.

Observed behavior: Sometimes the IO Device does not send the ApplicationReady in this sequence.

The issue will most likely occur if the Release sequence is started almost instantly after the second connection is estabished.