[Incomer]: Better handling of Dispatcher State

[Rossb0b]

The code below is used to check that previously published Events are well published. It only does it on the interval where the Incomer instance defined the Dispatcher as Alive.
If the Dispatcher is NOT Alive, we just skip until we receive a ping and so consider the Dispatcher instance as Alive.

Actually, this part of the code is useless as long as the Incomer and the Dispatcher share the same instance, yet, it is run for two reasons,

• If the Dispatcher class fails out, a new Dispatcher will take relay & so the pre-defined Incomer instance will start receiving ping events. At this moment, the Incomer isn't synchronized anymore with the Dispatcher, so running the function is a MUST-HAVE.
• If the Env var is wrong, again, the Incomer is not synced, and will receive ping events, so running the function is MUST-HAVE.

Actually, that part of the code works properly, but the two points I just raised are not highlighted in the code, so it makes it difficult to maintain.