Allow multiple QueryParameter filters for the same key with different properties

[aelfannir]

Description
Right now, if you add multiple #[QueryParameter] annotations with the same key but different properties and filter types, only the last one works, it overrides the earlier ones.

In real use cases, developers often need different filters for different fields under the same key. It would make more sense if each property could have its own filter, so filters only override each other when they target the same property.

Example

#[QueryParameter(
    key: ':property',
    filter: new ExactFilter(),
    properties: ['field1', 'field2'],
)]
#[QueryParameter(
    key: ':property',
    filter: new BooleanFilter(),
    properties: ['field3', 'field4'],
)]

[aelfannir]

A big reason this matters is simplicity. Right now, applying different filters to fields under the same key requires awkward workarounds like exact[:property] or partial[:property].

For example, a query like ?title=foo&status=todo&priority=medium naturally calls for a PartialSearchFilter on title and an ExactFilter on status and priority. Allowing filters to be unique per key + property would make APIs more intuitive, predictable, and easier to use.

[soyuka]

Looked at this. Two paths forward:

1. Bug fix (#8196) — your example as written silently dropped the first #[QueryParameter] attribute because Parameters::add / Parameters::__construct / MetadataCollectionFactoryTrait::mergeOperationParameters deduplicated by (class, key) before :property was expanded per-property. PR #8196 fixes that: repeated :property templates with disjoint properties lists now coexist, and each property resolves to its declared filter.

After #8196 your example works as written:

#[QueryParameter(key: ':property', filter: new ExactFilter(), properties: ['field1', 'field2'])]
#[QueryParameter(key: ':property', filter: new BooleanFilter(), properties: ['field3', 'field4'])]

2. Cleaner declaration model (#7870) — adds \Attribute::TARGET_PROPERTY to QueryParameter/HeaderParameter, letting each property carry its own attribute. Default key = property name. Rewrites the same use case as:

#[ApiResource]
class Task
{
    #[QueryParameter(filter: new PartialSearchFilter())]
    public string $title;

    #[QueryParameter(filter: new ExactFilter())]
    public string $status;

    #[QueryParameter(filter: new ExactFilter())]
    public string $priority;
}

?title=foo&status=todo&priority=medium routes each value to its declared filter. No :property placeholder, no key collision, no awkward exact[:property]/partial[:property] namespacing.

Closing once #8196 lands. #7870 stays open as the long-term ergonomics improvement.