Invalid Module Diff Block and Check Indications with unsorted Expected submodule blocks

If the RPC Connect.req() of a controller contains modules not sorted by api and slot, an invalid module diff block might be generated and unexpected Check Service indications might be sent to the host application.

The occurence of the problem depends strongly on the encoding of RPC connect.req() sent by the Profinet IO Controller.

It is expected that the protocol implementation accepts Expected Submodule blocks in any order.

Example when this issue occurs: Slot 0 uses API 0, Slot 1 uses a different API (not 0) and Slot 2 again uses Slot 0.