Add a precise cost of score in ScorerSupplier [LUCENE-10446]

Some queries could sometime actually provide a precise cost of Score like RangeFieldQuery, PointRangeQuery, SpatialQuery. maybe we could do some optimization by using this precise cost.

Like in IndexOrDocValuesQuery, when indexScorerSupplier or/and dvScorerSupplier's precise cost is reader.maxDoc, we will supply the right Scorer instead of according to the condition of threshold <= leadCost which sometime supply a inappropriate Score when IndexOrDocValuesQuery not a lead iterator.

---
Migrated from [LUCENE-10446](https://issues.apache.org/jira/browse/LUCENE-10446) by Lu Xugang (@LuXugang), updated Mar 03 2022
Attachments: [LUCENE-10446.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-10446/LUCENE-10446.patch), [LUCENE-10466-1.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-10446/LUCENE-10466-1.patch)

Start by reading ScorerSupplier and the IndexOrDocValuesQuery behavior described in the issue, then review the attached LUCENE-10446 patches for the intended direction. Verify how precise costs from RangeFieldQuery, PointRangeQuery, and SpatialQuery affect scorer selection, and use the relevant query tests to confirm the inappropriate scorer case is corrected.

Written by the indexing model from the issue text.