Fix test that assumed a certain order of doc IDs with equal score

If the score is equal in Lucene the order of the result depends on the
actual global doc ID such that due to background merges or concurrency
these test can return different result set orders.
Expose recursion level for Hunspell token filter. Closes #3369
Generate consistent random settings across nodes

IndexGatewayTests rely on that all nodes have the same type of
storage to pass consistently. Random configs should be the same for all
nodes in the cluster.
Fix CustomScoreSearchTest that assumed a certain order of doc IDs with equal score
Add facility to index in random order

Tests are more reproducible if documents are indexed in random order
with random flushes/refreshes etc. in order to catch corner cases
where doc Ids are used for tie-breaking and tests rely on a certain
order.
Fixed hang when submitting mappings and no changes are made

Added missing listener call before return

Closes #3381
Can't share XContentBuilder across threads.
break out if there no more liveIds. This can happen if another thread emptied the liveIds.
Added regression tests for #3381
0.90.3 uses lucene 44
Math is as hard as Concurrency
fix test to use correct store setting
Fixed test that relied on internal document ordering.

Lucene might internally tie-break on low level doc-Ids which
can change depending on merges etc. and test timings. No test should
rely on the actual order if scores are identical.
better handling of failures in transport to catch assertions
make sure we also catch assertions (well Throwable) in our transport layer and properly log or callback the exception handler in that case
Add a "score_mode" parameter to rescoring query.

Default value is "total", possible values are: "max", "min", "avg",
"multiply" and "total".

- "total": the final score of a document is the sum of the original
  query score with the rescore query score.
- "max": only the highest score count.
- "min": only the lowest score is kept (if the document doesn't match
  the rescore query, the original query score is used).
- "avg": average of both scores
- "multiply": product of both scores

Closes #3258
better handling of failures in transport to catch assertions
move wrapping the stream into the try block, even though its unlikely they will throw a failure, better be safe...
Only check if ttl purger has deleted the docs when the delete count in indexing stats has been increased.
pass the codec to fix index
its not used in Lucene fix index implementation, but just in case, pass it because we can (tm).
Added support for percolating an existing document.

The percolate an existing document feature executes an internal get operation to get the source of the document to percolate.

All options for percolating an existing document:
* `id` - The id of the document to percolate.
* `type` - The type of the document to percolate.
* `index` - The index to fetch the document to percolate from.
* `routing` - The routing value to use to retrieve the document to percolate.
* `preference` - Which shard to prefer (defaults to `_local`).
* `version` - Enables a version check. If the fetched document's version isn't equal to the specified version then the request fails with a version conflict and the percolation request is aborted.

All the option can be specified inside the `get` body part or via query string arguments.
Internally the percolate api will issue a get request for fetching the`_source` of the document to percolate.

For this feature to work the `_source` for documents to percolate need to be stored.

Closes #3380
cleanup signatures file