`TC001` - `TC003` should not apply with lazy imports

[stephenfin]

Summary

PEP 810 (Explicit lazy imports) specifically calls out lazy imports as eliminat[ing] the common need for TYPE_CHECKING guards. While TYPE_CHECKING may still have a use for avoiding circular imports, it's does cause a lot of issues for tools that rely on runtime behavior (think: sphinx.ext.autodoc, beartype, etc.). Would it make sense to deprecate these rules or discourage their use code bases that only support Python 3.15 or greater, on the basis that users would be better off using lazy imports to avoid these expensive imports?

[ntBre]

I think it would be a bit early to deprecate these rules since Ruff supports much older Python versions than 3.15, but it does make sense to me to adjust the rules to account for lazy imports, for example by suggesting a lazy import instead of moving to a TYPE_CHECKING block on 3.15 or later.

[stephenfin]

Agreed with adjusting the rules, though we could also deprecate the rules outright if target-version or project.requires-python indicated that the project under test only supported >= 3.15. That's what I was getting at with "[w]ould it make sense to deprecate these rules or discourage their use code bases that only support Python 3.15 or greater". At some point many (5 1/2?) years from now this will be true for everyone 😄