Fix: Timestamp Threshold Sweeps Ancestors of First Expired Catalog

This fixes a potential problem with timestamp based garbage collection where clients might run into I/O errors because legacy revisions were swept too early. We now keep the first revision that actually falls under a given timestamp threshold and remove everything that comes after it. Most of this pull request is unit test adaptions, though...