[recovery] fix: setRequestLocale ordering in resources page (static→dynamic error)

The resources page called getTranslations("page-resources") before ever
calling setRequestLocale(locale), and generateMetadata never called it at
all. Bot/invalid paths like /api/resources are captured by the [locale]
catch-all with "api" as the locale segment. Since that isn't a valid
locale in generateStaticParams, the route renders on-demand and next-intl
reads the locale from request headers, opting the route into dynamic
rendering and throwing:

  Error: Page changed from static to dynamic at runtime /api/resources,
  reason: headers

Fix: call setRequestLocale(locale) first in both Page and generateMetadata,
before any next-intl API. Same fix class as the wallets/videos pages.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: pettinarip

app/[locale]/resources/page.tsx

@@ -1,4 +1,4 @@
-import { getTranslations } from "next-intl/server"
+import { getTranslations, setRequestLocale } from "next-intl/server"
 
 import type { Lang, PageParams } from "@/lib/types"
 
@@ -35,6 +35,8 @@ const Page = async (props: { params: Promise<PageParams> }) => {
   const params = await props.params
   const { locale } = params
 
+  setRequestLocale(locale)
+
   const t = await getTranslations("page-resources")
 
   // Fetch data using the new data-layer functions (already cached)
@@ -237,6 +239,9 @@ export async function generateMetadata(props: {
   const params = await props.params
   const { locale } = params
 
+  // Set the locale before any next-intl API (getMetadata calls getTranslations)
+  setRequestLocale(locale)
+
   const t = await getTranslations("page-resources")
 
   return await getMetadata({