Reachability undermines offline reconnect logic

When working with the troublemaker proxy I notice that the following occurs when running a continuous push replication in the face of failure:

1. The failure happens, and in c4StatusChanged the replicator goes to offline.
2. At the end of handleError the reachability observer is started
3. The reachability observer immediately sends out a "network reachable" message as its initial message in the case that the network status is known
4. This triggers a callback to reachabilityChanged and since reachable is true and the replicator is offline, this causes an immediate retry