fix(doctrine): handle inverse side of OneToOne association in Doctrine search filter

[carlobeltrame]

Q	A
Branch?	main because @soyuka told me so, but ideally it should be for the current stable branch
Tickets	Same as #2049, but for SearchFilter instead of ExistsFilter
License	MIT

The same problem explained in #2049 also happens for the Doctrine SearchFilter. This PR fixes the SearchFilter, similarly to how #2051 fixed the ExistsFilter.

The issue can be reproduced by adding an Entity Dummy that has an owning one-to-one relation to another Entity RelatedOwnedDummy, and then adding a SearchFilter for that relation:

/**
 * @ORM\Entity
 */
#[ApiResource]
#[ApiFilter(SearchFilter::class, properties: ['relatedOwnedDummy'])]
class Dummy {

    /**
     * @ORM\OneToOne(targetEntity="RelatedOwnedDummy", mappedBy="owner", cascade={"persist"})
     */
    public ?RelatedOwnedDummy $relatedOwnedDummy = null;

}

Without this fix, Doctrine complains:
"A single-valued association path expression to an inverse side is not supported in DQL queries. Instead of "o.relatedOwnedDummy" use an explicit join."

• Always add tests and ensure they pass.
• Never break backward compatibility (see https://symfony.com/bc).
• Bug fixes must be submitted against the current stable version branch.
• Features and deprecations must be submitted against main branch.
• Legacy code removals go to the main branch.
• Update CHANGELOG.md file.
• Follow the Conventional Commits specification.

[soyuka]

Please rebase against main I want to freeze 2.6 from now on.

[carlobeltrame]

@soyuka done

[alanpoulain]

Thank you @carlobeltrame! I will merge 2.6 into main later.