…grekas)This PR was merged into the 3.4 branch.Discussion----------[DI] Fix "almost-circular" dependencies handling| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | yes| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#19362,#24775| License       | MIT| Doc PR        | -In a situation like the following one, we used to trigger a circular reference exception. But this was a false positive, as the reference is resolvable without hitting the circle. Fixing this exception could be considered as a new feature (because no existing config needs it, since it fails). But for 3.4, this should be considered a bug fix, as reported in#24775: not handling this situation now means creating broken service trees.``` php$containerBuilder = new ContainerBuilder();$container->register('foo', FooCircular::class)->setPublic(true)   ->addArgument(new Reference('bar'));$container->register('bar', BarCircular::class)    ->addMethodCall('addFoobar', array(new Reference('foobar')));$container->register('foobar', FoobarCircular::class)    ->addArgument(new Reference('foo'));$foo = $containerBuilder->get('foo');```Commits-------beb4df7 [DI] Fix "almost-circular" dependencies handling

…grekas)This PR was merged into the 3.4 branch.Discussion----------[DI] Analyze setter-circular deps more precisely| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | yes| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#24950| License       | MIT| Doc PR        | -This PR reverts the effect of#24828 and#24822 on fixtures, except for the new behavior these PRs introduced, which was mostly fine, but missed a few cases.This PR now uses the reference graph to precisely decide which services need circular dependency care, and does not touch the other ones.Commits-------9cc4a21 [DI] Analyze setter-circular deps more precisely