Currently, Time.tcl provide an onLoad procedure to initialize first the broker, then the notifications:

utimer 90 onload

proc onload {} {
        ::broker::init
        ::notifications::init
}

If ::broker::init fails, the procedure will stop without initializing notifications engine.

Afterwards, we'll fix broker connectivity but forgot about that one, so proposal is to move ::notifications::init to a callback for a new onBrokerInitialized event.

We should also document how to fix any broker connection issue, perhaps a .broker high-level command to restore connectivity and call the needed init methods could be nice.

Careful to not blindly call ::notifications::init: we don't want to call twice (or 3 times, 4 times, etc.) each callback function.