…rchers (#2146)

- When using the `Advance()` API on an `IndexSnapshotTermFieldReader`, a
special replacement mechanism is applied during a `Rewind`— when the
requested document ID is behind the current document ID pointed to by
the reader. In such cases, the object itself gets replaced.
- However, this approach fails when the `IndexSnapshotTermFieldReader`
is created by the `optimizeCompositeSearcher` method, which is used to
construct optimized `conjunction` or `disjunction` searchers.
- The issue arises because the `unadornedTermFieldReader` is initialized
with the `term` set to `<optimization-type>` and `field` set to `*`. As
a result, calling `Advance()` renders the entire `TFR` unusable, as it
gets replaced by a dummy `TFR` that no longer functions.
- This problem occurs specifically when calling `Advance()` on the
`unadornedTermFieldReader` with an ID less than the current posting ID
(triggering the rewind mechanism).
- The issue is resolved by resetting the underlying
`unadornedPostingsIteratorBitmap`, which effectively achieves the same
result as the `TFR` replacement technique without rendering it unusable.

- Add a Filter query for Boolean queries, which filters the document set
returned by the
Boolean query itself.
- The filter query does not affect scores, and any document returned by
the Boolean query
must also satisfy the filter query.
- The key difference between using a Filter query and placing an
equivalent query in the
Must clause is that queries in the Must clause contribute to the score.
The Filter
query is intended purely for filtering purposes without modifying the
document scores
set by the base Boolean query.
- Requires a Bug Fix (#2146)
to allow for the usage of the Advanced API in case the FilterQuery is an
optimized
composite searcher.
- Resolves #2037