On v7.0, when performing the collection validation check for the time ordering of a compressed time-series bucket, we do not properly track the previous timestamp seen. This can cause us to erroneously report the "Time-series bucket is v3 but has its measurements in-order on time" error.