Frequent GC can prevent nested catalogs from getting replicated

As discovered during the sft-nightlies storage migration, the replication of a nested catalog tree can stop prematurely if previous revisions of the parent catalog became unavailable due to GC on the source. As a result, if GC runs more frequently than snapshotting, parts of a nested catalog tree can remain missing on the snapshot destination.