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

The /wallets page (app/[locale]/wallets/page.tsx) called
getTranslations("page-wallets") before setRequestLocale(locale), and
generateMetadata never called setRequestLocale at all. For locales rendered
on-demand — e.g. a bot probe like /api/wallets where "api" is captured as the
[locale] param and is not covered by generateStaticParams — next-intl falls
back to reading the locale from request headers. That opts the route into
dynamic rendering and Next.js throws "Page changed from static to dynamic at
runtime /api/wallets, reason: headers" (stack shows get requestLocale) instead
of rendering statically.

Call setRequestLocale(locale) first in both the page and generateMetadata,
mirroring the fix in PR #18785 for the videos [slug] page.

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

Author: pettinarip

app/[locale]/wallets/page.tsx

@@ -41,10 +41,12 @@ import heroImg from "@/public/images/wallets/wallet-hero.png"
 const Page = async (props: { params: Promise<PageParams> }) => {
   const params = await props.params
   const { locale } = params
-  const t = await getTranslations("page-wallets")
 
+  // Set locale before next-intl APIs so on-demand renders stay static
   setRequestLocale(locale)
 
+  const t = await getTranslations("page-wallets")
+
   // Get i18n messages
   const allMessages = await getMessages({ locale })
   const requiredNamespaces = getRequiredNamespacesForPage("/wallets")
@@ -386,6 +388,9 @@ export async function generateMetadata(props: {
   const params = await props.params
   const { locale } = params
 
+  // Set locale before next-intl APIs so on-demand renders stay static
+  setRequestLocale(locale)
+
   const t = await getTranslations("page-wallets")
 
   return await getMetadata({