Fix precedence of negation vs comparison

[mntnorv]

Fixed antlr grammar to correctly prioritize negation vs comparison when parsing.

Before fix, expression !foo == 'bar' was parsed into:

Negate(Comparison(==, Property(Foo), String(bar)))

After fix, expression !foo == 'bar' is parsed into:

Comparison(==, Negate(Property(Foo)), String(bar))

Taking the JS implementation as the source of truth, because it prioritizes negation vs comparison. Example:

search(!foo == `true`, {"foo":1}) // false

First foo (which is equal to 1) is negated, resulting in false. Then, the result is compared to true, so the final result is false. Before the fix, this Java implementation would return true for the same expression, because first foo is compared to true, which results in false (because 1 != true) and the result is negated, resulting in true.

[iconara]

Hi. I'm not sure what makes this different from #69, but thank you for fixing this! Will this fix #65?

I'm sorry that I'm not very responsive when PRs come in, I don't have much time to spend on this, but I will get this merged and release, I just can't promise you when.

[mntnorv]

#69 had some unintended changes pushed and then removed, otherwise the change is the same. Regarding issue #65, I think it should have been solved by PR #66.