[paradoxalarm] Fix GenericCommunicator not reaching ONLINE after initialization

INITIALIZE_DATA.runPhase() guarded the entire body with an IParadoxCommunicator
instanceof check, so GenericCommunicator (used during Phase 1 panel auto-discovery)
never called nextState().runPhase() and therefore never transitioned to ONLINE.
This caused doPostOnlineTask() to time out and auto-discovery to fail.

Signed-off-by: Konstantin Polihronov <polychronov@gmail.com>

Author: theater

bundles/org.openhab.binding.paradoxalarm/src/main/java/org/openhab/binding/paradoxalarm/internal/communication/CommunicationState.java

@@ -318,6 +318,8 @@ protected void runPhase(IParadoxInitialLoginCommunicator communicator, Object...
                 // Transition to ONLINE is deferred until the first complete RAM read cycle
                 // completes (see EvoCommunicator.receiveRamResponse).
                 comm.initializeData();
+            } else {
+                nextState().runPhase(communicator);
             }
         }
     },