FEAT-#4622: Unify data type of log_level in logging module

[arunjose696]

What do these changes do?

• first commit message and PR title follow format outlined here

  NOTE: If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

• passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
• passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
• signed commit with git commit -s
• Resolves Unify type of log_level in logging module #4622?
• tests added and passing
• module layout described at docs/development/architecture.rst is up-to-date

[YarShev]

Suggested change

	"""Enumerator to Specify the valid values of LogLevel accepted by Logger.setLevel()."""
	"""Enumerator to specify the valid values of LogLevel accepted by Logger.setLevel()."""

Why noqa?

[arunjose696]

was getting traceback in doc_checker.py that {'value', 'names', 'start', 'type', 'module', 'qualname'} not documented, could see other intEnum using #noqa, so used this in this enum as well.

[YarShev]

Why changed?

[arunjose696]

In previous impl, as log_level was a string the logger was called as below,

logger_level = getattr(logger, log_level)
logger_level(start_line)

now as log level is not a string(but int) this has been changed to call
logger.log(log_level,message)