modify default backfill data parts order in ascending

[yl-lisen]

This close #508

[jovezhong]

Question, any impact to the seek_to behavior, are the auto-hist-backfill events sorted or not?

The current docs:
https://docs.timeplus.com/query-syntax#query-settings

1. enable_backfill_from_historical_store=0|1. By default, if it's omitted, it's 1.
   • When it's 0, the query engine either loads data from streaming storage, or from historical storage.
   • When it's 1, the query engine evaluates whether it's necessary to load data from historical storage(such as the time range is outside of the streaming storage), or it'll be more efficient to get data from historical storage(for example, count/min/max is pre-computed in historical storage, faster than scanning data in streaming storage).
2. force_backfill_in_order=0|1. By default, if it's omitted, it's 0.
   1. When it's 0, the data from the historical storage are turned without extra sorting. This would improve the performance.
   2. When it's 1, the data from the historical storage are turned with extra sorting. This would decrease the performance. So turn on this flag carefully.

[yl-lisen]

Question, any impact to the seek_to behavior, are the auto-hist-backfill events sorted or not?

The current docs: https://docs.timeplus.com/query-syntax#query-settings

1. enable_backfill_from_historical_store=0|1. By default, if it's omitted, it's 1.

   • When it's 0, the query engine either loads data from streaming storage, or from historical storage.
   • When it's 1, the query engine evaluates whether it's necessary to load data from historical storage(such as the time range is outside of the streaming storage), or it'll be more efficient to get data from historical storage(for example, count/min/max is pre-computed in historical storage, faster than scanning data in streaming storage).

2. force_backfill_in_order=0|1. By default, if it's omitted, it's 0.

   1. When it's 0, the data from the historical storage are turned without extra sorting. This would improve the performance.
   2. When it's 1, the data from the historical storage are turned with extra sorting. This would decrease the performance. So turn on this flag carefully.

@jovezhong The historical data is sorted in ascending for each internal data parts.
Currently, By default enable_backfill_from_historical_store=true, force_backfill_in_order=0, we will read these data parts in reverse order.

For example:
ingest data: parts1 (0-3), parts2 (3-4)

read in reverse: parts2(3-4), parts1(0-3)

after modified: parts1(0-3), parts1(3-4)