Implement "minimum number should match" on BooleanQuery about tantivy

[fulmicoton]

@LebranceBW I agree with both points.

The BooleanQuery -> BooleanWeight -> BooleanScorer are precisely here so that while users define their query by instanting a Query object, this query can be at runtime converted into different Scorer.

[LebranceBW]

I'm willing to implement this feature. However, my familiarity with this project is limited. Here are my initial considerations:

• The minimum_should_match functionality operates as an additional constraint on BooleanQuery. It appears that the existing UnionScorer cannot fit it. A novel scorer MinimumRequirementScorer based on UnionScorer needs to be developed, which rejects Doc missing conditions. minimum_should_match will be passed as one of it's member.
• To minimize performance impacts, the MinimumRequirementScorer,
  UnionScorer, and RequiredOptionalScorer will be employed under different BooleanQuery combinations.

Advices wanted. 😄