* fixes #257 - added $format arg to date histogram

* fixed typo

Example `['from' => 0, 'to' => 0]` is a valid aggregate range

There are situation where adding multiple queries is super beneficial. 

This PR enables package users to call `$search->addQueries(...)` in two different ways.

#### Single dimension array parameter

In this case an array of `BuilderInterface $query` are passed to the root `$search->addQuery()` function.

#### Multi dimensional array parameter

In this case an array of arrays is passed in, each member of the array is to match the function signature of `$search->addQuery()` and the PHP 5.4 traversable unpacking language feature is used to parameterise the root `$search->addQuery()` function.

(cherry picked from commit 8458ac9)

(cherry picked from commit 8600bf0)

* implemented relation for geo_shape query

* switched position and coordinates parameters

* Switched parameters for tests as well

* Deprecated parameter position

* Overwrite relation

'_source_exclude' and '_source_include' was missing in parameters whitelist.

* Getter for nested query.

Currently there is not possibility to get query object when it is wrapped inside nested query.

* Exposing path for nested query.

* Removing not needed space.

* added documentation for geo distance range query

* added a deprecation message to geo distance range query

* updated the readme

* copied the release info to changelog

* updated the how to section on filters

* updated the regexp queery docs: changed filter to query

* reorganized query docs

* added in progress... to new doc files

* bump development version number

* add scroll to URI parameters, fixes #201

* remove deprecated queries

* move tests

* added support for 5.x elasticsearch syntax

changed script_score lang to painless

* refactored tests to support elastic 5

* update changelog

* uri parameters was moved to container, introduced 5.0 new request body parameters

* removed filter endpoint, change order for query and postfilter

* search test has too many not necessary test cases

All those tests has to be in specific query or endpoint. Also functional tests make more sense then asserting it in the SearchTest

* moving elasticsearch/elasticsearch to required dependencies

# Conflicts:
#	src/Query/BoolQuery.php
#	src/Query/FunctionScoreQuery.php
#	src/Query/LimitQuery.php
#	src/Query/MissingQuery.php