fix(doctrine): ignore operator-map values in ExactFilter and PartialSearchFilter

[soyuka]

Q	A
Branch?	4.3
Bug fix?	yes
New feature?	no
Deprecations?	no
Issues	Fixes #8407
License	MIT
Doc PR	n/a

What

ExactFilter and PartialSearchFilter treated an associative (non-list) array value as an IN (...) list / a set of LIKE clauses. When one of them shares an HTTP key with an operator-map filter (ComparisonFilter, DateFilter), the operator-map form ?prop[lt]=x resolves the value to ['lt' => 'x'] for every parameter declared on that key — so the equality/partial filter injected a bogus prop IN ('lt' => ...) on top of the intended comparison, silently returning wrong results (usually zero rows).

Both filters now skip associative arrays: a non-list array is an operator map owned by ComparisonFilter/DateFilter, not equality.

if (\is_array($value) && !array_is_list($value)) {
    return;
}

Why

Reported in #8407: ExactFilter combined with DateFilter on the same property stopped working after migrating off SearchFilter, because ExactFilter fires on the bracketed date syntax too. The guard makes the equality/partial filters ignore value shapes that aren't theirs, so combining them with an operator-map filter fails safe.

Test

New functional test DoctrineTest::testExactFilterIgnoresOperatorMap() with a fixture declaring an ExactFilter and a ComparisonFilter on the same key: ?quantity=10 matches exactly, ?quantity[lt]=10 applies only the comparison. Fails before the guard (empty result), passes after. No regressions across tests/Functional/Parameters/.

[soyuka]

superseeds #8411