GeodeFilter is unable to handle predicates with where with Or And

If we pass a filter with combination of OR , AND GeodeFilter is unable to parse the query, instead it removes all the where clauses and ends up fetching the data from the entire region.

The query can be like below

(a = 1 OR a > 2) AND b = 4

This is scenario is documented as a TODO in GeodeBookStoreTest function name testWhereWithOrAnd