Better handling of cypher query results

[DenysVuika]

Right now when 'cypherQuery' call results in a multi-dimensional array that requires knowing all positions of the data in the result set. For example when executing "[...] RETURN user, roles" I would ideally expect accessing data in the callback via some getters, similar to the following: "result.data[0].user" or "result.data[1].roles" without the need using "result.columns" for that. This should greatly simplify scenarios related to raw cypher query calls.

[philippkueng]

Hi @DenisVuyka

Generally I tried keeping it as close to the original response from Neo4j since I didn't know how they develop their language. It's a good idea though; will investigate on how that can be implemented without breaking backwards compatibility.