Harden DB-reading pages with graceful fallback (no 500 without DB)

/news and six admin pages issued raw prisma reads with no try/catch, so
a DB outage rendered a 500 instead of an empty state. Wrap each read
(try/catch or .catch(() => fallback), preserving select() row types and
notFound() on the user-detail page). Matches the fail-soft pattern used
across the rest of the app.

Verified: tsc 0, next build 0, all public pages 200 against a dead DB.

src/app/admin/users/[id]/page.tsx

@@ -18,10 +18,12 @@ export default async function AdminUserDetail({
 }) {
   const { id } = await params;
   const userId = Number(id);
-  const user = await prisma.user.findUnique({
-    where: { id: userId },
-    select: { id: true, username: true, motto: true, rank: true, credits: true, look: true, online: true },
-  });
+  const user = await prisma.user
+    .findUnique({
+      where: { id: userId },
+      select: { id: true, username: true, motto: true, rank: true, credits: true, look: true, online: true },
+    })
+    .catch(() => null);
   if (!user) notFound();
 
   return (