optimize the pre-aggregation of out-of-order

**Describe the feature you'd like**

Currently, if the records arriving out of order are not located in the written time interval, they will be written to the table separately, which will affect the performance of pre-aggregation.

**Additional context**

https://github.com/4paradigm/OpenMLDB/blob/687b279e863afceb837d11bbe38bc5c3f37163f6/src/storage/aggregator.cc#L174

The issue points to src/storage/aggregator.cc line 174. Start by understanding the pre-aggregation logic and how out-of-order records are currently handled. Examine the code around that line to see where records outside the written time interval are written separately. Determine what 'optimize' means in this context—likely modifying the aggregation logic to batch or reorder these writes. Run existing tests related to aggregator to ensure changes don't break functionality.

Escrito por el modelo de indexación a partir del texto del issue.