Improve the Issues view

[git-afsantos]

This view is currently a very rough draft of what it needs to be. HAROS took a few steps in the right direction, but did not go far enough. It classified issues with a number of labels, and allowed users to filter the (potentially huge) list of issues by labels, by package, by being related to runtime architecture...

Some of these filters are useful, but I was thinking that perhaps we should start with huge blocks of issues (near duplicates, same reported issue in multiple places, or maybe broader categories). From there, we would navigate down to concrete reports with all the respective details. As if navigating a file tree. You start with directories, until you get down to the files.

It might be useful to look into other quality assurance dashboards, like SonarQube, and see how they currently handle this.