Initial commit for the global-phase rank-score-drop-limit

[dainiusjocas]

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Implements #31619

Continuation of #29955

The idea is to iterate through all hits in the global phase after re-ranking and drop those with a lower score than the set threshold.

Or should drop in the global phase work like in the second phase: drop within the reranked hits?

[arnej27959]

This looks good, but I'm not sure about the total-hit-count adjustment; if this feature is active you won't be able to get any further hits so maybe it should be clamped to the hits you actually keep.
Please run
mvn install -Dabicheck.writeSpec
in the container-search module to update the ABI spec (as you added some new public methods).

[arnej27959]

this looks good, we'll pull it in and I will make / extend a system test.

[dainiusjocas]

I didn't fully understand your point about the total-hit-count adjustment. Is it related to paging?

[arnej27959]

paging: yes - if you get a high total-hit-count it's expected that you can repeat the query asking for more hits (or with some offset) to get more results, but when this limit triggers all the hits below will be dropped as well. I'll test it and see how it looks, it's probably OK as-is.