mypy resolves symbol incorrectly with builtins import cycle

Context: https://github.com/python/typeshed/pull/6289

To reproduce:

1. check out typeshed
2. git checkout 9eabedca5f47a710f29d6e3e2b3a389853fab5aa
3. apply this patch

diff --git a/stdlib/builtins.pyi b/stdlib/builtins.pyi
index 2393f3c9..0d2ea882 100644
--- a/stdlib/builtins.pyi
+++ b/stdlib/builtins.pyi
@@ -717,6 +717,7 @@ class bool(int):
     def __rxor__(self, __x: int) -> int: ...
     def __getnewargs__(self) -> tuple[int]: ...
 
+@final
 class slice(object):
     start: Any
     step: Any

Then run:

mypy --python-version 3.10 --no-incremental --custom-typeshed-dir . stdlib/_ast.pyi stdlib/ast.pyi 

and note that mypy incorrectly resolves slice to builtins.slice instead of ast.slice in ast.pyi

Note that if you change the order of files, it works just fine:

mypy --python-version 3.10 --no-incremental --custom-typeshed-dir . stdlib/ast.pyi stdlib/_ast.pyi 

It's a pretty weird case, import cycle with builtins, collision with name in builtins, from _ast import * in ast.pyi, etc. But a scary kind of bug :-)

Comienza con la reproducción usando stdlib/builtins.pyi, stdlib/_ast.pyi y stdlib/ast.pyi en el commit 9eabedca5f47a710f29d6e3e2b3a389853fab5aa. Ejecuta ambos comandos de mypy con los dos órdenes de archivos y rastrea por qué ast.pyi resuelve slice como builtins.slice; se considera terminado cuando se corrija la resolución dependiente del orden que se ha informado, sin depender del orden de los archivos.