feat(frontend): refine ban list and communications block list

[maxijabase]

Description

UX polish pass across the public Ban List and Communications Block List:

• Denser tables with icon-only row actions (tooltips + aria-label), compact avatars, and tighter chrome
• Header actions aligned between banlist and comms (btn--sm, Lucide icons; banlist search icon parity)
• Advanced Steam search always uses partial LIKE match (drops Exact/Partial toggles; advType=steamid kept as legacy alias)
• Delete confirms use styled <dialog>s instead of window.confirm (ban delete, comm delete, comment delete)
• Comment chips sit on the same line as the player name (icon + count); name truncates so the chip does not wrap alone
• Avatar stays top-aligned next to the name when a comment disclosure is open

Motivation and Context

Banlist / commslist rows felt tall and uneven: comment badges forced an extra line under the player name, delete flows still used native confirms, and header / row action chrome drifted between the two lists. This brings both surfaces onto the same denser, more predictable pattern.

How Has This Been Tested?

• Manual checks on banlist + commslist (desktop): density, header buttons, inline comment chips, expanded-comment avatar alignment, delete dialogs
• PHPUnit assertions added/updated in BanlistCommentsVisibilityTest (head row + no __label)
• Related E2E touch-ups in comms-affordances / comment-delete-dispatcher

Screenshots

Before

---

After

---

Comment chip (collapsed / expanded)

---

Delete dialogs

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.