SOLR-16931: ReRankScaler explain breaks with debug=true and in distributed mode

[joel-bernstein]

https://issues.apache.org/jira/browse/SOLR-16931

Description

The ReRankScaler collects specific information for the explain when debugQuery is set to true. But the parameter debug=true doesn't trigger the collection of this data which causes an NPE in the explain.

The work around is to always use debugQuery=true until this ticket is resolved and released.

It turned out that this ticket had two problems. The first one is described above. The second issue is that distributed explain is broken with the ReRankScaler.

The reason for this is that in order to do proper explain for minMaxScaling you need to know the min and max score in the result set. This piece of state is maintained in the ReRankScaler itself which is inside of the ReRankQuery. But for this information to be populated the query must first be run. In distributed mode, explain is called in the second pass when the ids query is run so the state needed for the explain is not populated. The PR attached to this addresses this problem by doing a single pass distributed query if debugQuery is turned on and if reRank score scaling is applied. I'll add a distributed test for this as well.

This change is very limited in scope because the single pass distributed is only switched on in the very specific case when debugQuery=true and reRankScaling is on.

Checklist

Please review the following and check all that apply:

• I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
• I have created a Jira issue and added the issue ID to my pull request title.
• I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
• I have developed this patch against the main branch.
• I have run ./gradlew check.
• I have added tests for my changes.
• I have added documentation for the Reference Guide