fix: reject groups accumulator for distinct bitwise aggregates

[jackylee-ch]

Which issue does this PR close?

• N/A

Rationale for this change

bit_xor(DISTINCT c) with GROUP BY fails with Invalid argument error: column types must match schema types, expected List(Int16) but found Int16. groups_accumulator_supported ignored is_distinct, so the plan got the non-distinct PrimitiveGroupsAccumulator while state_fields declared the distinct List state. XOR is also not idempotent, so duplicates change the result: 5 ^ 5 ^ 9 = 9 but 5 ^ 9 = 12.

What changes are included in this PR?

groups_accumulator_supported now returns !args.is_distinct, matching sum, avg and count.

What is the testing strategy for this PR?

Two aggregate.slt queries covering the two shapes SingleDistinctToGroupBy does not rewrite (a non-distinct aggregate alongside, and a FILTER). Both fail on main with the error above and pass with this change.

Are there any user-facing changes?

bit_and/bit_or/bit_xor with DISTINCT and GROUP BY now return correct results. No API change.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.67%. Comparing base (5b389eb) to head (c779379).

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #24989      +/-   ##
==========================================
- Coverage   81.67%   81.67%   -0.01%     
==========================================
  Files        1126     1126              
  Lines      414524   414524              
  Branches   414524   414524              
==========================================
- Hits       338558   338545      -13     
- Misses      56054    56062       +8     
- Partials    19912    19917       +5     

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jayzhan211]

Thanks @jackylee-ch 👍🏻

Wait, I found an issue

[jayzhan211]

Should we limit operator to XOR only, since AND and OR are idempotent so DISTINCT does not change their result and they keep the vectorized path.

Also, do we need to handle null case? This could be a follow-up issue

Suggested change

	!args.is_distinct
	!(args.is_distinct && self.operation == BitwiseOperationType::Xor)