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/news/page.tsx

@@ -9,10 +9,16 @@ function formatDate(d: Date | null): string {
 }
 
 export default async function NewsPage() {
-  const articles = await prisma.websiteArticles.findMany({
-    orderBy: { createdAt: "desc" },
-    take: 30,
-  });
+  let articles: Awaited<ReturnType<typeof prisma.websiteArticles.findMany>> = [];
+  try {
+    articles = await prisma.websiteArticles.findMany({
+      orderBy: { createdAt: "desc" },
+      take: 30,
+    });
+  } catch {
+    // DB unavailable — render the empty state rather than a 500.
+    articles = [];
+  }
 
   return (
     <main>