fix(ui): distinguish catalog status icons

[lntutor]

Summary

Closes #1933.

• use a plain shield for clean scans, a shield with an exclamation for lower-severity findings, and a warning triangle for high or critical findings
• use a check-circle for trusted entries and a lock for verified ownership so those states no longer share the same glyph
• rebuild the checked-in catalog UI assets

Verification

• npm run check (0 errors; two pre-existing warnings)
• npm run build

npm run lint remains blocked by eight pre-existing Prettier failures in unrelated files.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[lntutor]

Current head 1d6df81f4471383c1d6a1f61508f1d88cf652ecc is mergeable, the visible CI/coverage/DCO checks on this head are green, and there are no unresolved review threads on the current PR state. This looks ready for maintainer review when convenient.

[csirmazbendeguz]

I have tested out this branch and I'm including the screenshots:

Safe=yes

Safe=yes, MaxSeverity=Medium (orange)

Safe=yes, MaxSeverity=Low (blue)

Safe=yes, MaxSeverity=None (green)

Safe=no, MaxSeverity=High,Critical

Safe=no, MaxSeverity=Critical (red)

Safe=no, MaxSeverity=High (dark orange)

Safe=no, MaxSeverity=Medium,Low,None

Safe=no, MaxSeverity=Medium (orange)

Safe=no, MaxSeverity=Low (blue)

Safe=no, MaxSeverity=None (green)

[csirmazbendeguz]

Thanks for your PR!

We have made some adjustments to the issue (#1933). I understand it wasn't 100% clear, we didn't consider the issue thoroughly and we only realized the problem after reviewing your PR

We decided to simplify the logic around the shield badges. Please check the issue and adjust your PR. Thanks!