Description of problem:

Messages are being displayed at issue level in static reports produced by the CLI. This was wrongly introduced in this PR. Messages in rules allow for placeholders and variable interpolation that is depending on the incident level, not the issue level. In this example, we can see the prefix, type and package custom variables being captured from each incident on match, and the message field containing placeholders that will be replaced according to the values captured on each incident, which allows rules authors to build messages custom tailored to the nature of each incident (in this case pointing to the exact offending class). Considering that rows in the Issues table display exactly that, Issues, and that messages are custom built for each incident related to that overarching issue, it doesn't make sense to display the message in there. What we do instead is display the full (customized) message on each incident when clicking on the affected files list, and only the description at issue level.

 Version-Release number of selected component (if applicable):

7.3.0. Also reproducible in 7.2.2.

 How reproducible:

 Steps to Reproduce:

1. Browse any issue in the issues table

Actual results:

Issue message is displayed.

Expected results:

Only issue description should be displayed at issue level.

Additional info:

Customer support case 04156225