As of SERVER-98477, when we attempt to insert a batch of measurements into a bucket and encounter a rollover reason, we rollover the original bucket and resume inserting into a newly allocated bucket. We should treat rolling over due to time differently - i.e, when we detect that inserting a measurement would cause a bucket to be rolled over, we should check and see if there is an existing "alternate" open bucket that has been marked with a rolloverAction of kArchive or kSoftClose that we can insert into