feat(doctrine): per-property filter map in FreeTextQueryFilter

[soyuka]

Q	A
Branch?	main
Bug fix?	no
New feature?	yes
Deprecations?	no
Issues	Refs #8249
License	MIT

Summary

Extend FreeTextQueryFilter (ORM + ODM) to accept either:

• a single FilterInterface — current behaviour, applied to every property;
• an array<string, FilterInterface> map — a dedicated filter applied per property.

The map form solves cases where a single filter can't fit every property — e.g. PostgreSQL native uuid columns break LOWER(uuid) emitted by PartialSearchFilter, while ExactFilter works fine on them.

'q' => new QueryParameter(filter: new FreeTextQueryFilter([
    'name' => new OrFilter(new PartialSearchFilter()),
    'uuid' => new OrFilter(new ExactFilter()),
]), description: 'Partial name match or exact uuid match'),

Single-filter signature is preserved, so the change is non-breaking.

When the map form is used, the iterated properties default to the map keys; the $properties constructor arg still takes precedence if set.

Test plan

• new functional test testFreeTextQueryFilterWithPerPropertyFilterMap covers partial-name vs exact-ean differentiation
• all 7 FreeTextQueryFilterTest cases pass on ORM
• ODM mirror executed in CI