Optimize sort on numeric long and date fields.

[mayya-sharipova]

This rewrites long sort as a DistanceFeatureQuery, which can
efficiently skip non-competitive blocks and segments of documents.
Depending on the dataset, the speedups can be 2 - 10 times.

The optimization can be disabled with setting the system property
es.search.rewrite_sort to false.

Optimization is skipped when an index has 50% or more data with
the same value.

Optimization is done through:

1. Rewriting sort as DistanceFeatureQuery which can
   efficiently skip non-competitive blocks and segments of documents.

2. Sorting segments according to the primary numeric sort field(Sort leaves on search according to the primary numeric sort field #44021)
   This allows to skip non-competitive segments.

3. Using collector manager.
   When we optimize sort, we sort segments by their min/max value.
   As a collector expects to have segments in order,
   we can not use a single collector for sorted segments.
   We use collectorManager, where for every segment a dedicated collector
   will be created.

4. Using Lucene's shared TopFieldCollector manager
   This collector manager is able to exchange minimum competitive
   score between collectors, which allows us to efficiently skip
   the whole segments that don't contain competitive scores.

5. When index is force merged to a single segment, Add a new merge policy that interleaves old and new segments on force merge #48533 interleaving
   old and new segments allows for this optimization as well,
   as blocks with non-competitive docs can be skipped.

Backport for #48804

Co-authored-by: Jim Ferenczi jim.ferenczi@elastic.co

[elasticmachine]

Pinging @elastic/es-search (:Search/Search)