fix(admin): avoid ~/modules/shared barrel in server-only router

The `~/modules/shared` barrel re-exports `useZodForm`, which imports
`useForm` from `react-hook-form`. Next.js picks the server build
(`react-server.esm.mjs`) for RSC / route handlers, and that build does
not expose `useForm` — so the indirect import chain
`adminStats.ts → shared barrel → useZodForm → react-hook-form` makes
`next build` fail on any server code that reaches the barrel.

Switch to a direct import from `~/modules/shared/nafSections` for the
two constants we actually need (DOMINANT_NAF_SECTIONS +
OTHER_NAF_SEGMENT) and document the trade-off inline so the next
server consumer doesn't re-hit the same trap.

Author: LucasCharrier

packages/app/src/server/api/routers/adminStats.ts

@@ -23,7 +23,15 @@ import {
 	getMultiYearGapTrendSchema,
 } from "~/modules/admin/stats";
 import { COMPANY_SIZE_RANGES } from "~/modules/domain";
-import { DOMINANT_NAF_SECTIONS, OTHER_NAF_SEGMENT } from "~/modules/shared";
+// Server-only router: import the constants directly from the internal file
+// instead of the `~/modules/shared` barrel, which also re-exports the
+// `useZodForm` client hook. The barrel pulls `react-hook-form`, and its
+// server build (`react-server.esm.mjs`) does not export `useForm`, so
+// indirect imports from server code break `next build`.
+import {
+	DOMINANT_NAF_SECTIONS,
+	OTHER_NAF_SEGMENT,
+} from "~/modules/shared/nafSections";
 import { adminProcedure, createTRPCRouter } from "~/server/api/trpc";
 import type { DB } from "~/server/db";
 import { companies, declarations } from "~/server/db/schema";