Geo log cursor processes events on the primary

If the Geo log cursor somehow gets enabled on a primary node, it reads events and schedules sidekiq jobs. It should not. Presumably this is also an issue when the machine is not configured as a geo node of any type. This can lead to data loss on the node.

We should ensure it does not try to do anything unless the current node is a secondary.