[flake8-logging] Implement LOG007: ExceptionWithoutExcInfo

[qdegraaf]

Summary

This PR implements a new rule for flake8-logging plugin that checks for uses of logging.exception() with exc_info set to False or a falsy value. It suggests using logging.error in these cases instead.

I am unsure about the name. Open to suggestions there, went with the most explicit name I could think of in the meantime.

Refer #7248

Test Plan

Added a new fixture cases and ran cargo test

[github-actions]

PR Check Results

Ecosystem

✅ ecosystem check detected no changes.

[qdegraaf]

Would it be worth it to check the name of the call first before calling resolve_call_path()for performance reasons? Or would that just add unnecessary clutter?

[konstin]

This needs to catch all log messages.

More common than

logging.exception("...")

is doing

logger = logging.getLogger(__name__)

logger.exception("...")

ruff has utils to detect logging calls, see is_logger_candidate and e.g. the G001 implementation.

[qdegraaf]

Rewrote to utilise is_logger_candidate. It flags logger.exception and logging.exception now but does not flag from logging import exception; exception() Is that a limitation of is_logger_candidate? And if so, do we want to create another branch of logic to catch those cases?

[konstin]

Moved this to #7502