EZP-22465: removed deprecated dependency
EZP-22465: removed circular dependency between FieldHandler and ContentType handler
EZP-22465: remove circular dependency between ContentHandler and LocationHandler
SetupWizard: add 'System check' step for travis
BDD: add rest server FeatureContext
BDD: add object 'manipulation'
BDD RestClient: add basic REST client for REST testing
Move REST Input Parser to REST/Common

Move REST Base Input Parser from Server to Common for reuse
BDD: add rest internal sentences (interface + implementation)
Fix EZP-22625: Circular reference on ezsettings.default.session_name
Merge pull request #794 from MLoureiro/fix_rest_input_parser

Move REST Input Parser to REST/Common
SetupWizard: fix bdd sentence to press buton
Merge pull request #788 from cleverti/bdd_fix_community_pr119

SetupWizard: add 'System check' step for travis
Merge pull request #796 from MLoureiro/bdd_rest_client

BDD RestClient: add basic REST client for REST testing
CS fix in GuzzleClient.php
Un-deprecate Location based Content criteria that works as intended

The orginal reason (applying to random content locations, see #701)
why this was deprecated does not apply to criteria that actually
filters on specific locations.

When it comes to visibility this is such a common use case
that it is rather documented that it will include content
if it has *any* location that is hidden or visible. We may
consider to add flag or changing default behavour so it
always check all locations. But current behavoiur has several use
cases as well, at least from permission perspective if visibility
becomes part of it. For other use cases use LocationSerach.
[Doc] Add deprecation doc for deprecated SortClauses and Criteria
Merge pull request #804 from ezsystems/undeprecated_criteria

Un-deprecate working Location based Content criteria
EZP-22542: update test for priority sorting
EZP-22542: fix field value converter to correctly preserve relation order