Lucene asynchronous disk writes for aeq can lead to data mismatch after compacting

Due to the way krf and drf oplogs are created/updated, if the aeq has disk synchronous as false, there is a window of time where a krf is rolled/created with the current region entries, but events that had been removed have not yet been written to the drf.

We should probably change the aeq to be disk sync = true. This will alleviate some of the data mismatch where we have potential extra keys after compacting the oplogs.