Flexible "standard" query parser parses on whitespace [LUCENE-7315]

Copied from #3679:

The queryparser parses input on whitespace, and sends each whitespace separated term to its own independent token stream.
This breaks the following at query-time, because they can't see across whitespace boundaries:

n-gram analysis
shingles
synonyms (especially multi-word for whitespace-separated languages)
languages where a 'word' can contain whitespace (e.g. vietnamese)

Its also rather unexpected, as users think their charfilters/tokenizers/tokenfilters will do the same thing at index and querytime, but in many cases they can't. Instead, preferably the queryparser would parse around only real 'operators'.

---
Migrated from [LUCENE-7315](https://issues.apache.org/jira/browse/LUCENE-7315) by Steven Rowe (@sarowe), 2 votes, updated Jul 20 2016
Attachments: [LUCENE-7315.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-7315/LUCENE-7315.patch)
Linked issues:
- #3679