Fix filters on nested associations and embedded properties

[Seb33300]

Same as #7295 with a different approach.

Fixes #7452 and #6664

In resolveNestedAssociations() I have extracted the logic handling nested associations from search to make it reusable in filters.
It also properly handles doctrine embeddables.

It's now possible to use associations in filters using the dot syntax:

    public function configureFilters(Filters $filters): Filters
    {
        return $filters
            // author is an association
            ->add(TextFilter::new('author.fullName', 'Author name'))
            // address is an Embeddable
            ->add(TextFilter::new('author.address.country', 'Author country'));
    }

[Seb33300]

Just found an issue with the EntityFilter + nested associations, I am investigating.

[Seb33300]

While extracting that logic from search, I also modified:

• $queryBuilder is nullable so the resolveNestedAssociations() method can be called to resolve the nested EntityDto & property name without applying the joins to the query (eg: EntityConfigurator use it to resolve the entity used to fetch choice list)
• $mustEndWithAssociation is used to allow property ending on an association field (eg: post.author instead of post.author.fullName) as required by EntityFilter

[Seb33300]

Issue on EntityFilter is now fixed

[Seb33300]

Without this fallback, AuthorWithMinPostsFilter was not working in the EasyAdmin demo project.

[Seb33300]

Note about this:

Instead of try/catch, it would be cleaner to check if the filter is unmapped.
This may be achieved by checking the related form option as suggested by EA documentation:
https://symfony.com/bundles/EasyAdminBundle/current/filters.html#unmapped-filters

However, it looks like previous code was working on unmapped fields even if the mapped option was not specified.
For example, the custom filter from EA demo is not defining the mapped option, and it still work:
https://github.com/EasyCorp/easyadmin-demo/blob/main/src/Admin/Filter/AuthorWithMinPostsFilter.php

And if we replace the try/catch by a check on the form type option, this may introduce a BC break on unmapped filter that does not specify the unmapped option, but this should also fix this bug: #6386

[Seb33300]

I created another PR for this:
https://github.com/EasyCorp/EasyAdminBundle/pull/7507/changes#diff-287eb8b7c5087e92a2fc0eeb7271981fae1393063c1ce9337ed9ff595f0331d5R239-R251