Schedule replication jobs if no transactional vote happened
If a transaction was registered, but no voter actually cast any vote, then we need to assume that a repository modification happened without us knowing about it at all. In such a scenario, it's thus important that we schedule replication jobs from primary to secondaries instead of aborting the transaction like we currently do.
Follow-up of !2355 (comment 376882241).