Tag cloud on reports need a severe facelift: sorting/grouping, highlighting and hiding/removal

### Problem Statement

Given in some scenarios (such as in PHP reporting) there are _many_ rows of tags, it's fair to say some are more important than others - like the main OS and user details. However, it's all mixed up and we have to look for what we want to... look into.

Main issues found:
- tag ordering is pretty useless, since they don't seem to have any specific logic - it's not alpha, nor grouped by topic. Client stuff should be separate from server stuff, and from request-related tags and user details, for instance.
- general and "very specific" tags are mixed together
- many default tags may be considered useless by specific teams, and yet we cannot remove them, cluttering even more the reports. For instance, the following ones make no sense for us, at least on our project, but still they get back if I remove them from the project config: logger (php..?), mechanism (generic..?), runtime.name (php.. oh really?!), server_name (wanted to remove this to make a set of server.name / server.domain, but wasn't able to).

### Solution Brainstorm

There should be a setting that would highlight, somehow, the most important tags we deem as so. This is very common on Support systems, where it's either a global setting to define which tags are on top, or each user defines what they prefer to see first.

Besides on the "how", some ideas strike me:
- a separate row with the "main" tags, maybe bigger, and the rest below
- important tags get different coloring, such as colored background instead of just a border
- either allow other tags to be removed, hidden, or receive less attention (such as less opacity), so rarely important stuff don't fight for attention with the most important or seldomly important things