Namespace packages and __init__ imports

--namespace-packages runs into an issue if we import from __init__.py explicitly.

For instance, given:

.
└── proj
    ├── __init__.py
    └── a.py

$ cat proj/__init__.py 
x: int

$ cat proj/a.py       
from .__init__ import x

$ cat proj/b.py
from proj.__init__ import x

running mypy will result in:

$ mypy proj --namespace-packages
proj/__init__.py: error: Source file found twice under different module names: 'proj' and 'proj.__init__'

This issue comes up at least twice in mypy_primer's corpus.

This is correct in that you do get two entries in sys.modules, but undesirable for this to block type checking

Reproduce the error with the shown proj/init.py, proj/a.py, and proj/b.py files using mypy proj --namespace-packages. Start by tracing namespace-package module discovery and how explicit __init__ imports are recorded. Done means this example no longer reports the duplicate source-file error while still type-checking the imports.