Cloud connector initialization and discovery logic fix

This build implements automatic discovery immediately after successful cloud connector initialization, while also covering the race case where the discovery service registers only after the bridge is already online.
In my local log, disabling/re-enabling the cloud connector now automatically emits the same discovery results as a manual Scan: 1 controller, 7 enabled zones, 7 schedules, and 2 flex schedules.