ES6 compatible queries

[orangejulius]

This PR uses the work in pelias/query#109 to convert our Elasticsearch queries into an ES6 compatible format.

The main change is that we can no longer set the phrase property on match queries. Phrase queries must now use the match_phrase query which makes the distinction between the two query types much more clear

Note: this PR is currently based on top of #1356, which should be merged first.

Closes #1261
Connects pelias/pelias#719

[orangejulius]

There are a bunch of acceptance test failures on this branch. Its possible that the previous queries were not being interpreted by Elasticsearch as match_phrase queries. Some investigation will be needed to decide how to proceed. We can turn all the match_phrase queries into match queries if we need to though.

[orangejulius]

Turns out the error was due to a subtle mistake while converting the queries to ES6:

api/query/view/phrase_first_tokens_only.js

Line 20 in d117af1

vs.var('input:name').set( tokens.join(' ') );

The input:name variable was being overridden due to a line that should have been removed. This actually didn't have any effect on the query, but did cause the max_character_count_layer_filter to exclude addresses since it believed the input text was only 3 characters. I'm struggling to figure out how to put a unit test in place to test for this scenario without creating an entire new fixture.

But the good news is that this code is now good to go!

[missinglink]

yea looks good to me