Star imports can't be redefined

Bug Report

Using mypy 0.820+dev.61c346230cf4960c9766f7c2b5bd3312b47f74da and Python 3.9.4:

# a.py

x: int
# and many more definitions

# b.py

from a import *

x: str  # Name "x" already defined (possibly by an import)
reveal_type(x)  # Revealed type is "builtins.int"

This caused us a lot of trouble in python/typeshed#5545 and leads to this horrible and hard to maintain import mess: https://github.com/python/typeshed/blob/6ee67483a30e178f243d3a9a5b5a9bb4b902901a/stdlib/socket.pyi

I understand the warning and I think it makes sense to have to suppress it with # type: ignore. But the the fact that the override behaves differently from runtime is quite problematic as evidenced by socket.py. This is an example from the standard library that relies on the fact that star imports can be overridden selectively.

a.py と b.py の再現から始め、その後、mypy による star import とそれに続く x のアノテーションの扱いを、Python の実行時の動作と比較します。socket.pyi の例を実際のケースとして使用し、選択的なオーバーライドとその revealed type を対象とする回帰テストを追加します。