Add Roles & Admin/Super-Admin interface

Per organized-ideas.md §6: role assignment, account ban/unban/delete, and
direct Admin/Super-Admin CRUD of public catalog entries outside the
submission workflow.

Backend:
- list_users_for_admin(): Super-Admin-gated SECURITY DEFINER function
  joining profiles + auth.users (username, email, role, banned_until) —
  auth.users isn't exposed through PostgREST, so this is the only way to
  list accounts at all.
- New Edge Function admin-user-action (ban/unban/delete), using
  @supabase/server's `auth: 'user'` mode to verify the caller's JWT, then
  Supabase Auth's Admin API for the actual mutation. This is deliberately
  an Edge Function rather than a Postgres function like everything else in
  this codebase: touching auth.users needs the Admin API, the stable
  documented interface, not a direct write to a schema Supabase manages
  internally. Self-action guard; verify_jwt = true at the gateway on top of
  the function's own JWT verification.
- 5 new pgTAP tests (43/43 total) for list_users_for_admin (Super-Admin-only,
  even regular Admins get 42501).
- CatalogRepository gains admin* methods (direct edit of a public port/cable/
  device entry, plus adminUnpublish which flips is_public rather than
  deleting) — the update methods were already ownership-agnostic (RLS's
  is_admin() clause is what actually permits it), so these are thin aliases,
  not duplicated logic.

Frontend:
- authStore/AdminUserRepository: minimal role plumbing, shared UserRole type.
- adminUserStore + AdminUsersModal: list/role-dropdown/ban/unban/delete,
  gated to Super Admin only via a new "Manage Users" TopBar button.
- PortTypeManager/CableTypeManager/DevicePalette: built-in entries now show
  direct "Edit"/"Unpublish" for Admins (regular Admin included, per §6's
  capability table — not Super-Admin-exclusive) instead of "Suggest edit";
  unpublish reuses the review-queue's impact-check RPC before confirming.
- DeviceTemplateEditor gains an `adminMode` save path alongside its existing
  submissionMode/resubmitId ones.

Verified: tsc -b and oxlint clean; supabase db reset + 43/43 pgTAP tests
pass; confirmed both new privileged endpoints (the SQL function and the
Edge Function) actually work through the real REST API via live curl
calls — signup, email confirm, role promotion, ban/unban/delete round
trips, self-action guard, non-super-admin rejection, and verify_jwt=true
compatibility all exercised directly, not just asserted.

src/data/SupabaseCatalogRepository.ts

@@ -1,7 +1,8 @@
 import { v4 as uuid } from 'uuid'
 import type { Catalog, CableType, DeviceCategoryDef, DeviceTemplate, Port, PortType } from '../domain/types'
-import { cableTypeToRow, deviceTemplateToRow, portTypeToRow } from './catalogRowMapping'
+import { CATALOG_TABLE_BY_ENTITY_TYPE, cableTypeToRow, deviceTemplateToRow, portTypeToRow } from './catalogRowMapping'
 import type { CatalogRepository } from './CatalogRepository'
+import type { CatalogEntityType } from './SubmissionRepository'
 import { supabase } from './supabaseClient'
 
 interface DeviceCategoryRow {
@@ -260,4 +261,28 @@ export class SupabaseCatalogRepository implements CatalogRepository {
     const { error } = await supabase.from('device_templates').delete().eq('id', id)
     if (error) console.error('Failed to remove device template from Supabase', error)
   }
+
+  // The update* methods above never check ownership themselves — RLS does,
+  // server-side, based on the caller's identity — so an Admin/Super-Admin
+  // direct edit of a public entry is *exactly* the same write, just
+  // permitted by a different branch of the same policy (`is_admin()`
+  // instead of "owns it and it's still private"). These are aliases, not
+  // separate logic, so the two paths can't drift apart.
+  adminUpdatePortType(id: string, patch: Partial<Omit<PortType, 'id' | 'custom'>>): Promise<void> {
+    return this.updatePortType(id, patch)
+  }
+
+  adminUpdateCableType(id: string, patch: Partial<Omit<CableType, 'id' | 'custom'>>): Promise<void> {
+    return this.updateCableType(id, patch)
+  }
+
+  adminUpdateDeviceTemplate(id: string, patch: Partial<Omit<DeviceTemplate, 'id' | 'custom'>>): Promise<void> {
+    return this.updateDeviceTemplate(id, patch)
+  }
+
+  async adminUnpublish(entityType: CatalogEntityType, id: string): Promise<void> {
+    const table = CATALOG_TABLE_BY_ENTITY_TYPE[entityType]
+    const { error } = await supabase.from(table).update({ is_public: false }).eq('id', id)
+    if (error) console.error('Failed to unpublish catalog entry in Supabase', error)
+  }
 }