Fix #91: remove escaping/decorating of dotted path Shredder produces

[tatu-at-datastax]

This PR removes escaping as initially added since it is no longer needed and complicates matching of filters.

It also adds basic integration test cases to validate that dotted notation filter matching now works.

[ivansenic]

I am not sure if this works in all cases. I generally don't understand why are we not using the standard json path notation, where arrays are represented as:

path.array[0]

and there is clear distinction between

path.array.0

[ivansenic]

What when the node type is not known, for example if I do a $set on some.path.1 and path is not existing in the some object. Will the path be array or object?

[tatu-at-datastax]

JsonPath is only used for query index / matching, not for Update operations. Update operations will require more advanced handling, but they have context document (document to update) for that decision.
I will not be using JsonPath there -- although there's also possibility that since JsonPath is so simplistic we may just go back to String for this use case unless we find need for something beyond String.

[maheshrajamani]

LGTM

[tatu-at-datastax]

I am not sure if this works in all cases. I generally don't understand why are we not using the standard json path notation, where arrays are represented as:

path.array[0]

and there is clear distinction between

path.array.0

This is because path we build here needs to match Mongo/Mongoose "dot notation" which is simplistic: the only use case is to build index fields (query_text_values etc).

I agree that for any other use case (esp. if we had to reconstruct document) we would use something that guarantees uniqueness.