com.atproto.sync.listReposByCollection
scatter crawled resyncs to the future at qps limit
instead of a two-level queue keyed at the top by host to acheive round-robin requests by pds host, keep track of pds hosts last-queue-time when inserting, spreading them into the future so that new hosts get mixed in early
or another way:
schedule per-host resyncs as early as possible per-host but no earlier