Replace ALL with ANY in whilst querying relationship equality

[darrellwarde]

Description

Fixes Cypher generation when checking for equality of fields on related nodes, replacing ALL with ANY to return expected results. See linked issue for example.

ALL still used for _IN and _NOT_IN filters, which I believe is the correct behaviour.

Issue

#190

Checklist

The following requirements should have been met (depending on the changes in the branch):

• TCK tests have been updated
• Integration tests have been updated
• CLA (https://neo4j.com/developer/cla/) has been signed

[johnymontana]

I think the ANY is the right approach here. Using the movie example from the tests - when filtering for movies that are in the "Action" genre, you will have movies connected to multiple genre nodes and you only want to apply a predicate that says the movie has at least one relationship to the "Action" genre node, not that all genre relationships are to the "Action" genre node.

An alternative would be to create additional where filtering inputs such as genres_some, genres_every, genres_single, etc that map to the various Cypher list predicate functions. I don't think exposing each of these list predicates is the approach to take here though as I think the vast majority of use cases users are wanting the ANY logic applied and the additional list predicate options add confusion and leak Cypher specific concepts to the GraphQL layer.

[oskarhane]

Looking at the integration tests, this seems like the right thing to do.
I think Wills point on creating more fine grained filters if requested sounds sensible, while keeping this as a default.

🌻