Fix JSONPath syntax error with in filter after other filters

[caglareker]

Summary

Fix a parser error that occurred when using an 'in' filter in combination with other filters in JSONPath expressions. The parser was unconditionally requiring a closing parenthesis after parsing filters, which caused syntax errors when the 'in' filter's own parentheses were present.

Changes

Modify the filter parsing logic in JSONPathParser to only enforce the closing parenthesis requirement when the filter expression itself is wrapped in parentheses. This allows 'in' filters with their own parenthetical syntax to work correctly after other filter conditions.

Testing

Add test cases validating:

1. An 'in' filter used after other filter conditions (e.g., @.field=='value' && @.type in ('01','04'))
2. An 'in' filter used before other filter conditions

Both scenarios now parse and evaluate correctly.

Fixes #3997

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[caglareker]

My bad, I can't sign the CLA. Closing this one!

[jujn]

LGTM. Thank you for your contribution! If you're really unable to sign the CLA, I think we can make an exception and merge it anyway. Please reopen it.

[caglareker]

hey @jujn, i resubmited as #4001 since i already deleted the fork. same exact changes