Always build "what" from the original tokens.

We were already using the original tokens when a connector is present.
We now use the original tokens for connector-less queries, too.
make logback work

we didn't have a triggering policy, which a rolling logger needs

Auditors: rahul
Indexer bug fixes

1. Revert to single insert: Bulk insert will fail the entire batch if a
   duplicate key exception is encountered for any document. This is causing
   almost half the postal code features to not be imported.
2. Synchronization fix: Countdown revgeo latch only after all revgeo coverage
   workers are done rather than as soon as Done message is received from
   PolygonLoader

Auditors: nsanch, blackmad
my hands do not work. fix invalid logback.xml
Code Review feedback

Auditors: nsanch, blackmad
a bunch of little optimizations to geocoding

seems to take "san jose, san jose" down from 1s to 400-600ms
"san juan san juan" from >500ms to <300ms

open to other suggestions. These queries are hard because they end up making ~200,000 calls, and the list construction/copying is hard. It looks like just making the lists is one of my biggest hotspots left: http://cl.ly/image/0h0S3e1B170c

Auditors: rahul, nsanch, jliszka
toList -> toVector

shaves another 50ms off a 400ms query

Auditors: jliszka, rahul, nsanch
stupid hack?

don't test/create parses where woeTypes are equal, since we never have a city parented by a city etc.

Auditors: nsanch, rahul
no idea why the ListBuffer makes us throw that error

but it does

Auditors: nsanch, rahul
zero out WKB simplified in geocoder.html

Auditors: rahul
always return requestGeom in debug mode

useful for debugging when you pass a query + a hint ll and want to see how far away the hint is from it.

Auditors: rahul
simplify + fix lots of things about geocoder.html

1) use history.pushState, and stop using fragments, which were annoying
2) respect maxInterpretations in the url
3) have an ll and a query box
4) submit-on-enter
5) rely on request geom from the server
6) deprecate a few dumb params that we were just rewriting to other param names
7) some minor visual tweaks

makes the logic ever so slightly cleaner. would be awesome to use the thrift-js here, but I don't think that's happening anytime soon.

Auditors: rahul
0.82.15 bump
simplify(?) comparator function and use near float equality

maybe this is causing instability?

hopefully a no-op.

Auditors: rahul, nsanch
I'm an idiot, ints are equal
fix tests
stop using custom ivy path
two small perf spots that might have synchronization issues
Revert "fix bounds distance"

something in this s2 logic slowed the server to a crawl?

This reverts commit 2a18fc8a80ead2fdf90224902a9471fca71c5044.
.17 bump for ll/bounds exception

Auditors: rahul, nsanch