Idea: Pyreverse should distinguish between functional imports and type checking imports

[nickdrozd]

Current problem

Pyreverse generates a graph that depicts the import dependencies between modules. But it doesn't distinguish between imports that are used for runtime functionality and imports that are used only for type checking (that is, imports behind the TYPE_CHECKING flag).

Desired solution

It would be neat if different kinds of import dependencies were distinguished on the graph. For example, regular imports could be notated with a straight line (as is currently the case), while type imports could be notated with a squiggly line. Then it would be possible to tell at a glance what sort of relationship different modules really have.

Additional context

No response

[nickdrozd]

This would be especially handy in conjunction with #8111.