Nested search fields with same relational property name lead to missing JOIN statements

[ServerExe]

Imagine having the following entities:

class GiroAccount 
{
    #[ORM\Column]
    private string $name;

    /** @var Collection<int, GiroAccountDetail> */
    #[ORM\OneToMany(targetEntity: GiroAccountDetail::class, mappedBy: 'giroAccount')]
    private Collection $details;

    /** @var Collection<int, GiroAccountCard> */
    #[ORM\OneToMany(targetEntity: GiroAccountCard::class, mappedBy: 'giroAccount')]
    private Collection $cards;
}

# ---------------------------

class GiroAccountDetail 
{
    #[ORM\Column]
    private string $name;
}

# ---------------------------

class GiroAccountCard
{
    #[ORM\Column]
    private string $name;

    /** @var Collection<int, GiroAccountCardDetail> */
    #[ORM\OneToMany(targetEntity: GiroAccountCardDetail::class, mappedBy: 'card')]
    private Collection $details;
}

# ---------------------------

class GiroAccountCardDetail
{
    #[ORM\Column]
    private string $name;
}

Now, you can see that there are relational properties with the name "details". This is causing an issue when chaining them in the search fields:

->setSearchFields([
    'name',
    'details.name',
    'cards.details.name',
])

... will simply ignore a JOIN statement for GiroAccount::$details. The query looks like this then:

FROM giro_account g0_
LEFT JOIN giro_account_card g1_ ON g0_.id = g1_.giro_account_id
LEFT JOIN giro_account_card_detail g2_ ON g1_.id = g2_.card_id

... instead of ...

FROM giro_account g0_
LEFT JOIN giro_account_detail g1_ ON g0_.id = g1_.giro_account_id
LEFT JOIN giro_account_card g2_ ON g0_.id = g2_.giro_account_id
LEFT JOIN giro_account_card_detail g3_ ON g2_.id = g3_.card_id