Work around orphan records

An orphan record is possible when all the parent versions are GC for a given replicated timestamp (i.e. all remaining parent versions exist at a later timestamp). Now we always initiate replication from store (use the current consistent timestamp at the subscription creation as subscription end timestamp upper bound) and switch to live transaction log replication when the subscription end timestamp is reached.