174bf521

By: Tom Sydney Kerckhove <syd@cs-syd.eu>

Report each suppression in an unread file, not the file

A suppression in a file no rule is ever run over was one complaint per file,
pointing at line one. What somebody has to go and remove is a comment, so a
comment is what the report has to point at, and two suppressions in one such
file are two things to remove rather than one.

The scan now answers with a span per suppression. It asks meansToBeOne itself
rather than matching the same markers a second time, which also means a line
that mentions an allowlist before writing a real suppression is read the way the
parser would read it.
e2e-added-rule-is-rune2e-artifacts-are-reade2e-choices-are-found-beside-the-repositorye2e-cleane2e-dirty-package-is-judged-failinge2e-dirty-project-is-judged-failinge2e-dirty-report-is-readablee2e-disabled-rule-is-not-rune2e-incomplete-artifacts-are-a-failuree2e-judging-nothing-failse2e-named-packages-are-every-packagee2e-no-packages-is-judged-failinge2e-no-store-paths-in-findingse2e-paths-are-repository-relativee2e-withheld-facts-faile2e-wrong-source-mapping-is-a-complainthlint-checkhopinionpre-commitreleaseshellweeder-checkconfiguredevShelldefaultx86_64-linux