Make the analyzer comment readable

[dignajar]

The comment on #1 was hard to act on, so this is a pass over how a finding is presented and how it is worded.

Before

**`languages/en.json`** — `description` differs: the submission says `HTML editor for
formatting content, a lightweight WYSIWYG alternative to Markdown.`, `languages/en.json`
says `HTML Editor for formatting content. Lightweight WYSIWYG alternative for the users
who don't want to work with Markdown code.`.  `LANG_MISMATCH`
The directory lists the submission, Bludit shows this file once the plugin is installed.
A visitor would read two different texts.

Both values are inside one sentence, so comparing them means reading the line to the end twice. The header points at languages/en.json, but the file to change might be the submission.

After

The English description does not match the plugin  LANG_MISMATCH

• plugins/jodit.json — HTML editor for formatting content, a lightweight WYSIWYG alternative to Markdown.
• jodit/languages/en.json — HTML Editor for formatting content. Lightweight WYSIWYG alternative for the users who don't want to work with Markdown code.

Somebody browsing the directory reads the first one, and then sees the second once they install the plugin. Make them the same, or say in this pull request which one is right.

What changed

A finding can carry its values. New optional detail on a finding, a list of label and value pairs, rendered one per line. Both filenames are named, so it is clear there are two places and either could be the one to fix.

The source rules stopped repeating the location. Every one of them put the file and line inside the message while the header already showed both, so the problem itself landed at the end of the line. plugin.php uses eval() on line 7. → plugin.php:7 — Uses eval().

The advice assumed you knew the answer. SRC_ECHO_INPUT said to pass the value through Sanitize::html(); it now says a crafted link would otherwise run script on your site. ID_BUNDLED said to choose another id; it now says every site already has that plugin and installing over it would replace part of Bludit.

Repeated advice prints once per section. Two fields disagreeing used to print the same paragraph twice.

Checks

No code changed meaning, so all 63 fixtures pass unchanged — 12 corpus, 35 submission, 16 payload. Rendered both a warnings-only comment (jodit, from its real release asset) and an error-heavy one (a plugin calling eval, an assembled function name, an unescaped $_GET, and three fields disagreeing with its zip).