Add an osTicket integration: list open tickets from its database

osTicket's own REST API only supports creating tickets, not listing or
reading them, so this reads osTicket's MySQL/MariaDB database directly
with a read-only user instead - the only integration in this app that
isn't a REST API. Joins the ticket, status, priority, department,
staff, team, and user tables, filtered to tickets in the "open" state
(status names are customizable per install, but that state flag isn't).

Surfaces per-ticket subject, priority, department, assignee, requester,
and osTicket's own overdue/awaiting-reply flags, plus a page at
/osticket and a Dashboard widget with open/overdue/awaiting-reply
counts.

Not verified against a live instance: unlike the HTTP-based
integrations, there was no way to fake a MySQL server to test against
in this environment, so the query is built from osTicket's published
schema but has never actually run against a real database. See
INTEGRATIONS.md for the read-only grant needed and further caveats.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

web/src/App.tsx

@@ -21,6 +21,7 @@ import Proxmox from "./pages/Proxmox";
 import Synology from "./pages/Synology";
 import UptimeKuma from "./pages/UptimeKuma";
 import PbsBackup from "./pages/PbsBackup";
+import OsTicket from "./pages/OsTicket";
 import Generator from "./pages/Generator";
 import Maintenance from "./pages/Maintenance";
 import Domains from "./pages/Domains";
@@ -107,6 +108,7 @@ export default function App() {
         <Route path="/synology" element={<Synology user={user} />} />
         <Route path="/uptime-kuma" element={<UptimeKuma user={user} />} />
         <Route path="/pbs" element={<PbsBackup user={user} />} />
+        <Route path="/osticket" element={<OsTicket user={user} />} />
         <Route
           path="/users"
           element={