When argument_resolver.request was bumped to priority 120 (above argument_resolver.request_attribute at 100) to keep type-hinted Request arguments from triggering DoctrineBundle's EntityValueResolver, it silently broke the long-standing $this->forward(B::class, ['request' => $modified]) pattern: the matching attribute no longer wins over the sub-request.

Have RequestValueResolver and SessionValueResolver honor a matching named attribute themselves when its value matches the argument type. Non-matching names and non-matching types still short-circuit early enough to keep EntityValueResolver from running for Request arguments.