Description

Backport of #8205 to 8.6.

Describe the changes in the pull request

A clear and concise description of what the PR is solving, including:

1. Current:
   When the document insertion order doesn't match the score order returned by the vector RANGE query, the query returns no results instead of the expected matches.

Root Cause

• RANGE queries in FT.HYBRID are always combined with a filter (either explicit like @description:blue or implicit "*") via a PHRASE node in the AST.
• The PHRASE node creates an intersection iterator that uses SkipTo operations to efficiently find documents existing in all child iterators.
• SkipTo requires child iterators to be sorted by document ID.
• The bug: RANGE queries were returning results sorted BY_SCORE (by vector distance). When the score order differs from the document ID order (which is determined by insertion order), the SkipTo operations fail to find matching documents because they assume sorted-by-ID iteration.

2. Change:
   We implemented a conditional approach based on whether an explicit FILTER clause is provided:

• RANGE + explicit FILTER → Use BY_ID ordering (required for intersection iterator compatibility)
• RANGE without explicit FILTER → Use BY_SCORE ordering and skip filter integration so the vector node becomes the root directly

3. Outcome:

• FT.HYBRID VSIM RANGE + FILTER returns right results independent of docs ingestion order.
• test_hybrid_vector_range_with_filter was failing if the docs were ingested in different order of the vector results, now it works independent of ingestion order.

Which additional issues this PR fixes

1. MOD-13884

Main objects this PR modified

1. ...

Mark if applicable

• This PR introduces API changes
• This PR introduces serialization changes

Release Notes

• This PR requires release notes
• This PR does not require release notes

If a release note is required (bug fix / new feature / enhancement), describe the user impact of this PR in the title.