Changes typing for logging level to accept both str and int

[heavelock]

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.
• [x ] I accept that @willmcgugan may be pedantic in the code review.

Description

The standard logging module accepts either str or int as a logging level. str is internally casted to int. Rich does not do anything with the logging level so there is no reason to limit the type here.

[codecov]

Codecov Report

Merging #461 (0e201ec) into master (d2fe147) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #461   +/-   ##
=======================================
  Coverage   99.72%   99.72%           
=======================================
  Files          54       54           
  Lines        4654     4654           
=======================================
  Hits         4641     4641           
  Misses         13       13           

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

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

Impacted Files	Coverage Δ
rich/logging.py	100.00% <100.00%> (ø)
rich/pretty.py	100.00% <100.00%> (ø)
rich/prompt.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 8a8250c...fbedb8f. Read the comment docs.

[heavelock]

Black is complaining in CI at file I did not touch and when I am trying to run it on my system it does not complain.

[willmcgugan]

That's my fault. I'll fix that. Thanks for the PR.