Query Elevation based on Filter Query "fq" field

[BMouhcine]

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

Description

This PR introduces a new Query Elevation related feature.

Currently, QueryElevationComponent is implemented and can be used to configure/customize the top results for a given query, depending on the field query "q" .

This patch suggests an extension of this feature that allows users to configure the top results, based on the Filter Query field "fq" as well.

Solution

The Query Elevation based on Filter Query "fq" field is configured in the same way as for query field "q".
Here's an example of a <query> element in elevate.xml schema.

  <query text="cat:electronics"> 
    <doc id="TWINX2048-3200PRO" /> 
    <doc id="VDBDB1A16" />   
    <doc id="EN7800GTX/2DHTV/256M" />
  </query>

As for the query:

Having all of this, by running the SOLR query, the elements/documents defined in the elevate.xml schema snippet above, will be returned in the top of the results list.

Tests

Tests written and run alongside the Query Elevation Tests that already exist.
The files concerned are: QueryElevationComponentTest.java and elevate.xml.

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

[github-actions]

This PR had no visible activity in the past 60 days, labeling it as stale. Any new activity will remove the stale label. To attract more reviewers, please tag someone or notify the dev@solr.apache.org mailing list. Thank you for your contribution!

[github-actions]

This PR is now closed due to 60 days of inactivity after being marked as stale. Re-opening this PR is still possible, in which case it will be marked as active again.