False positive with namespace aliasing

[alamirault]

Hello,

Maybe somebody has an idea in order to avoid this false positive (found by https://github.com/symfony-tools/code-block-checker/blob/main/src/Service/CodeRunner/ClassExist.php)

---

https://github.com/symfony/symfony-docs/actions/runs/7431226718/job/20221747353?pr=19383

        // src/Entity/Author.php
        namespace App\Entity;

        use Symfony\Component\Validator\Constraints as Assert; # False positive here

        use Symfony\Component\Validator\Mapping\ClassMetadata;

        class Author
        {
            // ...

            public static function loadValidatorMetadata(ClassMetadata $metadata): void
            {
                $metadata->addPropertyConstraint('mac', new Assert\MacAddress());
            }
        }

[Missing class] Class, interface or trait with name "Symfony\Component\Validator\Constraints" does not exist

[stof]

We should probably make a special case for use Symfony\Component\Validator\Constraints as Assert and use Doctrine\ORM\Mapping as ORM which are the 2 common cases used in the documentation where we use a namespace rather than a class. It should be enough for our needs.