Match spotter for all query types [LUCENE-1999]

Related to #3004 and the current inability to highlight NumericRangeQuery, spatial, cached term filters and other exotica.

This patch provides the ability to wrap **any** Query objects and record match info as flags encoded in the overall document score.
Using this approach it would be possible to understand (and therefore highlight) which fields matched clauses in a query.

The match encoding approach loses some precision in scores as noted here: http://tinyurl.com/ykt8nx7

Avoiding these precision issues would require a change to Lucene core to record docId, score AND a matchFlag byte in ScoreDoc objects and collector APIs.
This may be something we should consider.

---
Migrated from [LUCENE-1999](https://issues.apache.org/jira/browse/LUCENE-1999) by Mark Harwood (@markharwood), updated Apr 14 2012
Attachments: [matchflagger.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-1999/matchflagger.patch)

Start with the attached matchflagger.patch and the related #3004 and LUCENE-1999 discussions. Review how the proposed query wrapping records match flags in document scores, then clarify the required Lucene core changes and score-precision trade-offs before defining completion criteria.

Written by the indexing model from the issue text.