Suggest API - bugs with encoding multiple levels of geo precision.
1) One issue reported by a user is due to the truncation of the geohash string. Added Junit test for this scenario
2) Another suspect piece of code was the “toAutomaton” method that only merged the first of possibly many precisions into the result.

Closes #7368
[CORE] Don't update indexShard if it has been removed before

Today we have logic that removes a shard from the indexservice if
the shard has changed ie. from replica to primary or if it's recovery
source vanished etc. This can cause shards from been not allocated at
all on a nodes causeing delete requests to timeout since we were waiting
for shards on nodes that got dropped due to a IndexShardMissingException

Closes #7509
Completion suggestion javadocs
[DOCS] Added JavaDocs for ClusterAdminClient, IndicesAdminClient and Warmer API
Docs: added missing jdocs for the percolate client classes.

Also made constructors were possible package protected
and removed some useless getters in percolator source builder.
Highlighter Javadocs
Docs: Add javadocs to the client-side aggregation APIs.
[TEST] fix off-by-one error in BigArrays tests

Comparisons for the BigArrays breaker use "greater than" instead of
"greater than or equal", which was never an issue before because the
test size was not right on a page boundary. A test with an exactly
divisible page boundary (4mb exactly in this case) caused the sizes to
be equal to, but not exceed, the limit, and never break.

The limit should be smaller than the test increments the breaker anyway.
[TEST] Stabelize SimpleRecoveryLocalGatewayTests#testReusePeerRecovery
[TEST] Remove unused plugin isolation leftover
[Tests] add different node name prefix for the different cluster type

During a test run we have a global shared cluster and potentially a suite level or even a test level cluster running. All of those share the same node name pattern (node_#). This can be confusing if you're debugging discovery related tests where those nodes from the different clusters potentially interact (and reject each other). This commit gives each cluster type a unique prefix to make tracing and log filtering simpler.

Closes #7518
Aggregations: The nested aggregator should iterate over the child doc ids in ascending order.

The reverse_nested aggregator requires that the emitted doc ids are always in ascending order, which is already enforced on the scorer level,
but this also needs to be enforced on the nested aggrgetor level otherwise incorrect counts are a result.

Closes #7505
Closes #7514