[recovery] fix: setRequestLocale ordering in [...slug] generateMetadata

The catch-all [locale]/[...slug] generateMetadata never called
setRequestLocale before invoking next-intl APIs. getMdMetadata ->
getMetadata calls getTranslations("common"), and the catch block also
calls getTranslations("common"). Without setRequestLocale, next-intl
reads the locale from request headers for on-demand slugs, opting the
route into dynamic rendering and throwing "Page changed from static to
dynamic at runtime ... reason: headers".

Observed in production via /images/videos/Clw-qf1sUZg.jpg, which maps to
the catch-all with locale="images".

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

Author: pettinarip

app/[locale]/[...slug]/page.tsx

@@ -154,6 +154,13 @@ export async function generateMetadata(props: {
   const params = await props.params
   const { locale, slug } = params
 
+  // Set the locale before any next-intl API (getMdMetadata -> getMetadata and
+  // the catch-block getTranslations both call getTranslations). Otherwise
+  // next-intl reads the locale from request headers and opts the route into
+  // dynamic rendering, triggering "Page changed from static to dynamic at
+  // runtime" for on-demand slugs not covered by generateStaticParams.
+  setRequestLocale(locale)
+
   try {
     return await getMdMetadata({
       locale,