feat(admin): practice domain settings, treatment case list and platform domain CRUD

Completes the panel side. A clinic picks its practice domain in settings, where
the copy says plainly that this is not the specialty label the public site shows;
picking nothing stays valid and changes nothing.

Cases and the unbooked queue share one page rather than two, because they answer
the same question — which patient is where in their course and what is still
owed. The queue explains why booking is not automatic instead of leaving the
reader to wonder.

Platform admins get domain CRUD with a column showing whether a domain has a
dedicated workflow or falls back to the default, so the gap is visible rather
than guessed at; the code field is locked after creation because workflows bind
to it.

Also puts the staff session screens in the sidebar — they were reachable only by
typing the URL.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

assets/admin/types/index.ts

@@ -1270,6 +1270,17 @@ export interface CatalogCategory {
     children?: CatalogCategory[];
 }
 
+export interface PracticeDomain {
+  uuid: string;
+  /** لنگرِ پیاده‌سازی workflow؛ بعد از ساخت تغییر نمی‌کند. */
+  code: string;
+  name: string;
+  sort_order: number;
+  active: boolean;
+  /** آیا پیاده‌سازی اختصاصی دارد یا رفتار پیش‌فرض می‌گیرد. */
+  has_workflow?: boolean;
+}
+
 // ── Treatment ────────────────────────────────────────────────────────────────
 
 export type TreatmentSessionStatus =