Show the dependency graphs for projects

[sschuberth]

The distinction between "Dependencies" and "Packages" on the menu-level seems to be too artificial. As "Dependencies" is still empty anyway, the idea is to remove it completely. Afterwards, "Packages" should be renamed to "Dependencies" (also taking the latter's icon), as "Dependencies" seems to be the more common term for users.

Later, once #944 is implemented, the "Dependencies" page should get a graph view in addition to the table view, probably on a separate tab (similar to like in the WebApp report).

[sschuberth]

As "Dependencies" is still empty anyway, the idea is to remove it completely.

That part was actually already done in c00df08.

[mnonnenmacher]

I wonder how we should deal with very large dependency trees, we already know from the web app reporter that they can cause memory issues in the browser. Implementing some kind of lazy loading could be very complicated, should we maybe always use the "deduplicate dependency tree" option for the UI to mitigate the issue?

[sschuberth]

should we maybe always use the "deduplicate dependency tree" option for the UI to mitigate the issue?

Sounds reasonable for display-purposes to me. The various package manager CLIs do the same.