Add AUR-Malware detail view: per-finding source, dismiss reviewed false positives

[Percius04]

Hi! This is a follow-up on top of #2 rather than another fix, so I opened it as a separate PR instead of folding it in — happy to do it differently if you'd prefer it as part of #2, or merged after, whatever's easiest for you to review.

Problem

The main popup only has room for a status word and a one-line summary ("2 failures, 1 warning out of 18 checks"). It never says WHICH checks failed or why — finding out means running the scanner by hand in a terminal.

Detail view

A "View detail" button (shown when there are findings, same back-button pattern as the existing Settings view) opens a breakdown:

• Grouped by source when one can be identified: a known-infected package name (straight from the scanner's own output), an npm/bun malicious-indicator package name, the package owning a flagged file path (pacman -Qo), or the comment sitting above a flagged /etc/hosts entry — e.g. a deliberate CurseForge/Overwolf telemetry block shows up labeled as exactly that, not as an unexplained wall of text. Ungrouped findings fall back to "OTHER", sorted after the named groups.
• Each finding shows its check name, fail/warn icon+color, and full detail text.

Dismiss / reactivate a reviewed false positive

• Only for checks that are heuristic and prone to false positives. Checks that are direct evidence of an actual compromise — known-infected package, malicious npm/bun indicator, eBPF artifacts, hidden processes, pacman log hits, ld.so.preload injection, persistence artifacts — have no dismiss button at all, full stop. This is what makes dismiss safe on a malware-detection tool: you can silence noise, never the signal that actually matters.
• Identified by check name + a hash of the exact detail text — if the detail changes (a new infected package shows up, a date moves), the old dismissal stops matching and the finding is active again on its own.
• The badge color and summary count only active (non-dismissed) findings — otherwise dismissing a known false positive wouldn't stop the badge going red for the same thing every 6h.
• qs-security-dismiss.sh recomputes the existing status file directly instead of rerunning the scanner (~13s for the network fetch + all 18 checks) — dismissing is bookkeeping over an already-run scan, it doesn't need a fresh one to show up in the badge.

Tested end-to-end on a real machine, including dismissing/reactivating actual findings and confirming the badge/summary update instantly without a rescan. Thanks for taking a look, and no worries at all if you'd rather take this in a different direction!