Stop rich.live from importing same module under a different name

[Jackenmen]

Type of changes

• Bug fix
• New feature
• Documentation / docstrings
• Tests
• Other

Checklist

• I've run the latest black with default args on new code.
• I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
• I've added tests for new code.
• I accept that @willmcgugan may be pedantic in the code review.

Description

Rich instead of importing from the top-level package using the module name alone, uses module name with __init__ which makes it get imported twice (under names: rich and rich.__init__).

Minimal reproduction:

import sys

import rich.live

print(sys.modules["rich"])
print(sys.modules["rich.__init__"])

I found out about it because mypy is complaining about it just because I use rich in my project. However, even if you skip that, this could still possibly lead to some strange issues when depending on the fact that modules in Python are singletons.

[codecov]

Codecov Report

Merging #912 (9e881e5) into master (d4d087c) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #912   +/-   ##
=======================================
  Coverage   99.54%   99.54%           
=======================================
  Files          58       58           
  Lines        5059     5059           
=======================================
  Hits         5036     5036           
  Misses         23       23           

Flag	Coverage Δ
unittests	99.54% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
rich/live.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a1e9cc7...9e881e5. Read the comment docs.