Related to #3095 a little.

As a package author, it's important to me that I don't drag in too many dependencies for my consumers. The more packages I need, the more risk of version conflict. On the other hand, during development time, there's no cost to me adding packages.

It would be great if the Dependencies toolwindow was able to disambiguate these two classes of package dependency. For example, it could be a filter to say "only show runtime dependencies", or perhaps a different icon (although this would be tristate, since some packages may be transitively depended on in both development and runtime scenarios).

See image below as an example: