[TEST] Replaced RestTestSuiteRunner with parametrized test that uses RandomizedRunner directly

ElasticsearchRestTests extends now ElasticsearchIntegrationTest and makes use of our ordinary test infrastructure, in particular all randomized aspects now come for free instead of having to maintain a separate (custom) tests runner

We previously parsed only the tests that needed to be run given the version of the cluster the tests are running against. This doesn't happen anymore as it didn't buy much and it would be harder to support as the tests get now parsed before the test cluster gets started. Thus all the tests are now parsed regardless of their skip sections, afterwards the ones that don't need to be run will be skipped through assume directives.

Fixed REST tests that rely on a specific number of shards as this change introduces also random number of shards and replicas (through randomIndexTemplate)

Closes #5654
[TEST] null out static resources in base test classes
[TEST] specified number_of_shards 5 to make sure the two docs end up in different shards that can be refreshed separately
Make writePrimitive*() and readPrimitive*() methods public.

These utility methods are useful for client code to read/write arrays of
primitive types.
Update LongHash to work like BytesRefHash.

- rename "key" to "get"
- update and add more tests

Closes #5693
Rename readPrimitive*Array()/writePrimitive*Array() methods

Make method names shorter and easier to read.

Closes #5711
Author: Sean Gallagher
Date: Tue Apr 1 12:28:00 2014

Added upgrade.asciidoc and links to it from setup.asciidoc

Author: Sean Gallagher
Date: Apr 1 2014

Added upgrade.asciidoc

Add upgrade instructions
Author: Sean Gallagher
Date: 4/4/14
Closes issue #5651

Fixed upgrade.asciidoc typo and incorrect usage.
Author: Sean Gallagher
Date: 4 Apr 2014
Closes 5651
[TEST] Be more verbose if ClusterStatsTests fails
Make sure successful operations are correct if second phase is fast

In TransportSearchTypeAction we  need to increment successful ops
first before we increment and compare the exit condition otherwise if we
are fast we could concurrently update totalOps but then preempt one
of the threads which can cause the successor to read a wrong value from
successfulOps if second phase is very fast ie. searchType == count etc.
This can cause wrong success stats in the search response.
Rename successulOps to successfulOps in TransportSearchTypeAction
[TEST] return the correct transport instance in mock transport
Fixes typo in "Scan" search type documention
[BUILD] Remove site dependencies generation

Removed dependencies library generation.  It stalls Jenkins static analysis job
[TEST] use no replicas in MLT tests - doc mappers need to be present on all nodes
Text Query has been replaced by Match Query

Closes #5727.
[TEST] make BulkTest more robust if test infra is slow
[TEST] Add more randomization to bulk tests
Failed shards could be re-assigned to the same nodes if multiple replicas failed at once

After a shard fails on a node we assign a new replica on another node. This is important in order to avoid failing again due to node specific problems. In the rare case where two different replicas of the same shard failed in a short time span, we may fail to do so and assign one of them back to the node it's currently on. This happens if both shard failed events are processed within the same batch on the master.

Closes #5725
[TEST] Wait for LANGUID events to be processed before pulling stats
[TEST] Log where locks are created from if they are still open on close()