revert(whitelabel): drop force-dynamic from landing layout

Cascading force-dynamic neutered dynamicParams = false + generateStaticParams on /blog/[slug], /integrations/[slug], /models/[provider], /models/[provider]/[model] — killing static prerender for SEO-critical pages. The hydration concern only materializes for whitelabel Docker deployments where build-time and runtime NEXT_PUBLIC_BRAND_* differ; those deployments can set the vars at build instead. Keeping force-dynamic on /privacy, /terms, and /manifest where it actually matters.

Author: waleedlatif1

apps/sim/app/(landing)/layout.tsx

@@ -16,11 +16,6 @@ export const metadata: Metadata = {
   },
 }
 
-/** Opt the landing segment out of static prerendering so client components like
- * Navbar render with the live runtime env (e.g. Docker-injected `NEXT_PUBLIC_BRAND_*`)
- * during SSR, avoiding hydration mismatches against `window.__ENV`. */
-export const dynamic = 'force-dynamic'
-
 /**
  * Landing page route-group layout.
  *