feat(i18n): translate hardcoded strings across print, public recipe, and recipe management UI

Wires dozens of components and server pages to next-intl instead of hardcoded
English text, and adds a lightweight getMessages/formatMessage helper for
server components (print pages, public recipe page, cook metadata) since
next-intl/server isn't wired into this app's routing. Backfills missing
en/fr message keys that existing code already referenced but fr.json lacked.

apps/web/app/(app)/recipes/[id]/cook/page.tsx

@@ -3,13 +3,16 @@ import { headers } from "next/headers";
 import { auth } from "@/lib/auth/server";
 import { db, recipes, eq, and } from "@epicure/db";
 import { CookingMode } from "@/components/cooking-mode/cooking-mode";
+import { getMessages, formatMessage } from "@/lib/i18n/server";
 
 type Params = { params: Promise<{ id: string }> };
 
 export async function generateMetadata({ params }: Params) {
   const { id } = await params;
+  const session = await auth.api.getSession({ headers: await headers() });
+  const m = getMessages((session?.user as { locale?: string } | undefined)?.locale);
   const recipe = await db.query.recipes.findFirst({ where: eq(recipes.id, id) });
-  return { title: recipe ? `Cooking: ${recipe.title}` : "Cooking Mode" };
+  return { title: recipe ? formatMessage(m.cookingMode.pageTitle, { title: recipe.title }) : m.cookingMode.pageTitleFallback };
 }
 
 export default async function CookPage({ params }: Params) {