magento/magento2#32292: Fix FilterPool crash on non-AbstractDb collections

[swnsma]

Fixed Issues

1. Fixes Custom admin UI component grid breaks when collection is not AbstractDb #32292 — Custom admin UI component grid breaks when collection is not AbstractDb

Manual testing scenarios

1. Create or use an admin UI listing whose data provider collection extends Magento\Framework\Data\Collection only (not AbstractDb), registered on CollectionFactory.
2. Open the admin grid (or call Reporting::search / mui/index/render for that namespace).
3. Expected: grid loads without Call to undefined method ...::getSelect(); filters apply via addFieldToFilter.
4. Regression: open a standard DB-backed grid (e.g. Customers) and apply multi-filter OR groups — results still match MC-24195 behavior.

Questions or comments

FilterPool::applyFilters() was rewritten in 2.4.2 (MC-24195 / 2638e0ff) to regroup SQL WHERE parts for correct OR-within-filter-group semantics. That path requires AbstractDb::getSelect(), but the method still type-hints base Collection.

This change:

• Keeps the SQL regrouping path for AbstractDb collections
• Restores the pre-2.4.2 applier-only loop for non-database collections
• Adds unit tests for both paths and an integration test for non-AbstractDb collections (existing ReportingTest continues to cover DB OR groups)

Related: #33119 (Braintree Settlement duplicate of the same root cause).

[m2-assistant]

Hi @swnsma. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[swnsma]

@magento run all tests