Relational operators on nested fields in flat collections

[suddendust]

Description

This Adds support for CONTAINS, NOT CONTAINS, IN and NOT IN operators for nested json fields for flat collections.

Testing

Added integration tests for all relational operators in FlatCollectionJsonbRelationalOperatorTest.

Checklist:

• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• Any dependent changes have been merged and published in downstream modules

[codecov]

Codecov Report

❌ Patch coverage is 90.00000% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.41%. Comparing base (704c275) to head (51a6a62).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...ter/PostgresNotContainsRelationalFilterParser.java	87.50%	0 Missing and 1 partial ⚠️
...er/filter/PostgresNotInRelationalFilterParser.java	83.33%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #243      +/-   ##
============================================
+ Coverage     80.10%   80.41%   +0.31%     
- Complexity     1134     1151      +17     
============================================
  Files           215      215              
  Lines          5488     5495       +7     
  Branches        482      486       +4     
============================================
+ Hits           4396     4419      +23     
+ Misses          764      750      -14     
+ Partials        328      326       -2     

Flag	Coverage Δ
integration	80.41% <90.00%> (+0.31%)	⬆️
unit	57.74% <85.00%> (+0.40%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[suddendust]

@suresh-prakash I tried avoiding this instanceof check but using a visitor just to check this seems like an overkill. Do you think we can avoid this using some other method?

[suresh-prakash]

Can use a strategy pattern and pass the object instance via. PostgresQueryParser.

[suresh-prakash]

Discussed this offline. @suddendust will plan to pick this up separately.