QueryParser with new features for Lucene 3 [LUCENE-1823]

I'd like to have a new QueryParser implementation in Lucene 3.1, ideally based on the new QP framework in contrib. It should share as much code as possible with the current StandardQueryParser implementation for easy maintainability.

Wish list (feel free to extend):

1. **Operator precedence**: Support operator precedence for boolean operators
2. **Opaque terms**: Ability to plugin an external parser for certain syntax extensions, e.g. XML query terms
3. **Improved RangeQuery syntax**: Use more intuitive <=, =, >= instead of [] and {}
4. **Support for trierange queries**: See #2842
5. **Complex phrases**: See #2560
6. **ANY operator**: E.g. (a b c d) ANY 3 should match if 3 of the 4 terms occur in the same document
7. **New syntax for Span queries**: I think the surround parser supports this?
8. **Escaped wildcards**: See #1666

---
Migrated from [LUCENE-1823](https://issues.apache.org/jira/browse/LUCENE-1823) by Michael Busch, 7 votes, updated May 09 2016
Attachments: [lucene_1823_any_opaque_precedence_fuzzybug_v2.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-1823/lucene_1823_any_opaque_precedence_fuzzybug_v2.patch), [lucene_1823_foo_bug_08_26_2009.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-1823/lucene_1823_foo_bug_08_26_2009.patch)
Linked issues:
- #3013
- #1453
- #1245
- #2071
- #2072
- #1666
- #2025
- #2641
- #2842
- #3678
- #4416
- #2895
- #6269
- #3114
- #2560
- #4203