Add ALL and EXACTLY_ONE array filter operators for MongoDB and Postgres

[lrathod]

Note: This PR continues from #323 (same change, now from an upstream branch so CI runs normally). All review discussion and resolutions are in #323.

Summary

Adds two new ArrayOperator values for filtering on array-valued attributes:

• ALL — array attribute must contain every value specified in the filter. Set-containment semantics: order and duplicates are irrelevant on both sides ([red, red] ALL [red] is true).
• EXACTLY_ONE — array attribute must contain exactly one element, and that element must be one of the specified values. The cardinality check counts raw elements, not distinct values ([red, red] EXACTLY_ONE [red] is false).

Both work on top-level and nested array fields (e.g. props.colors, scope.environmentScope.environmentIds), on MongoDB and Postgres.

MongoDB

• ALL → {"$expr": {"$setIsSubset": [<values>, <guarded array>]}}
• EXACTLY_ONE → $and of $size == 1 and $in on $arrayElemAt [path, 0]
• Non-array guard: <guarded array> is {"$cond": [{"$isArray": "$path"}, "$path", []]} — documents holding a missing/null/non-array scalar value simply do not match instead of erroring ($setIsSubset/$size reject non-array operands), matching the Postgres behaviour.

Postgres

• Native array columns (flat collections): ALL → col @> ?; EXACTLY_ONE → array_length(col, 1) = 1 AND col && ?. No COALESCE — NULL arrays are excluded by WHERE semantics anyway, and the unwrapped column reference keeps the filter GIN-indexable (SARGable).
• JSONB array paths (nested documents): ALL → (CASE WHEN jsonb_typeof(path) = 'array' THEN path ELSE '[]'::jsonb END) @> ?::jsonb; EXACTLY_ONE → jsonb_array_length(<guarded>) = 1 AND <guarded> <@ ?::jsonb (single bound param — with exactly one element, membership ≡ containment). The runtime jsonb_typeof guard is retained only for schemaless JSONB paths.
• Compile-time element types: the array element type is resolved from the field expression's DataType (ArrayIdentifierExpression#getElementDataType()), falling back to inference from the filter values only when the field carries no type info.

Design note

Both parsers require the inner RelationalExpression to carry a constant value list; a non-constant RHS throws UnsupportedOperationException. This is intentional — ALL/EXACTLY_ONE are set-level operators, unlike ANY which supports arbitrary per-element sub-filters. Empty value lists are rejected at construction by ConstantExpression.

Future consideration (noted in the enum javadoc): an EXACTLY operator for set equality — array contains exactly the filter values, no more and no less.

Test coverage / EXACTLY_ONE semantics

MATCH_EXACTLY_ONE describes the stored array cardinality, not the length of the RHS:

• Stored array must have exactly 1 element
• That element must be in the RHS list (RHS can be 1 or many candidates)

Example with column tags:

• Entity A: ["A", "B"]
• Entity B: ["A"]
• Entity C: ["B"]
• Entity D: ["A", "B", "C"]

Query	Result
MATCH_ALL ["A", "B"]	A and D (D matches because extras are allowed; ALL is subset / containment)
MATCH_EXACTLY_ONE ["A"]	B only
MATCH_EXACTLY_ONE ["A", "B"]	B and C (not A, not D — size ≠ 1)

Same translation on both stores: Mongo $size=1 + $in; Postgres native array_length=1 AND && / JSONB length + <@.

Test plan

• MongoArrayFilterParserTest — operator structure, $isArray guards, nested paths, non-constant RHS rejection, no double $expr wrapping
• PostgresQueryParserTest — ALL/EXACTLY_ONE × JSONB/native array, nested JSONB paths, compile-time type precedence over value inference, UNSPECIFIED fallback, non-constant RHS rejection
• DocStoreQueryV1Test (nested ArrayMatchAllOneOperatorTest) — integration tests on both datastores: nested JSONB array fields, native array columns (typed + untyped via PostgresArrayTypeProvider), JSONB array column on flat collections, 3-level nested paths with missing intermediate objects, non-array scalar values, duplicates ([red, red]), and order-independence — run in CI
• :document-store:build (compile + unit tests + spotless) passes locally

Made with Cursor

Nested arrays

• Nested arrays: operators apply to the outermost array only — an element that is itself an array is opaque and never matches a scalar RHS value; RHS lists are scalar-only. Pinned by IT testAllAndOneTreatNestedArrayElementsAsOpaque.

[github-actions]

Test Results

  127 files  + 2    127 suites  +2   39s ⏱️ -4s
  889 tests +34    888 ✅ +34  1 💤 ±0  0 ❌ ±0 
1 259 runs  +67  1 258 ✅ +67  1 💤 ±0  0 ❌ ±0 

Results for commit cc785ec. ± Comparison against base commit 64e8bc1.

♻️ This comment has been updated with latest results.

[codecov]

Codecov Report

❌ Patch coverage is 85.32110% with 16 lines in your changes missing coverage. Please review.
✅ Project coverage is 81.16%. Comparing base (64e8bc1) to head (cc785ec).

Files with missing lines	Patch %	Lines
...1/vistors/PostgresFilterTypeExpressionVisitor.java	82.66%	7 Missing and 6 partials ⚠️
...ore/mongo/query/parser/MongoArrayFilterParser.java	90.62%	2 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #326      +/-   ##
============================================
+ Coverage     81.06%   81.16%   +0.10%     
- Complexity     1617     1679      +62     
============================================
  Files           243      243              
  Lines          7656     7762     +106     
  Branches        755      769      +14     
============================================
+ Hits           6206     6300      +94     
- Misses          960      967       +7     
- Partials        490      495       +5     

Flag	Coverage Δ
integration	81.16% <85.32%> (+0.10%)	⬆️
unit	58.50% <85.32%> (+1.34%)	⬆️

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

☔ View full report in Codecov by Harness.
📢 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]

LGTM. Review here: #323