The specific failure mode that "flx: bootstraps contain all changes" is trying to exercise is no longer valid in the same way in qbsv2 vs qbsv1. The overall behavior of a bootstrap not containing all the possible changes that were in server history at the time the bootstrap completed is still valid, but the cause of getting snapshots from the broker cache has gone away in qbsv2. We should convert this test to ensure that we see the multi-message bootstrap followed by a MARK message and that we sequence sending a MARK message with sending a QUERY message appropriately.