fxiing the completelu pbroken production

[l-you]

The primary fix is that bug. Finally I've got a time to fix it. Blog has lost all the SEO traffic since then. 0 pages indexed remaining.

⨯ Error [ChunkLoadError]: Failed to load chunk server/chunks/_0nvsoa2._.js from runtime for chunk server/app/(payload)/api/graphql/route.js
    at loadRuntimeChunkPath (.next/server/chunks/[turbopack]_runtime.js:740:23)
    at loadRuntimeChunk (.next/server/chunks/[turbopack]_runtime.js:708:9)
    at Object.c (.next/server/chunks/[turbopack]_runtime.js:899:25)
    at Object.<anonymous> (.next/server/app/(payload)/api/graphql/route.js:5:3) {
  [cause]: SyntaxError: Invalid regular expression: /[^\w-]+/gv: Invalid character class
      at <unknown> (.next/server/chunks/_0nvsoa2._.js:1456)
      at loadRuntimeChunkPath (.next/server/chunks/[turbopack]_runtime.js:732:30)
}

fix(cms): upgrade toolchain and stabilize dev runtime

Summary

• Upgrade the CMS toolchain around pnpm, TypeScript 6, Lexical, Payload codegen, and generated GraphQL types.
• Fix TypeScript 6/runtime compatibility issues in localized GraphQL enum usage, URL detection, Payload search sync typing, and MDXEditor rich text wiring.
• Make the devcontainer/nginx setup more reliable by resolving upstreams dynamically and allowing OrbStack dev origins.
• Remove stale Prettier setup now that Biome owns formatting.

Testing

• task validate
• task codegen
• pnpm run next:typegen
• Payload migrations applied and verified locally with migrate:status
• Smoke-tested /admin and Micro_posts GraphQL through direct Next and nginx proxy

Risks

• Broad dependency and generated-code churn.
• Dev proxy changes require restarting the devcontainer/nginx stack to pick up the new config.

Migration

• No new migration file in this PR.
• Local dev DBs still need existing Payload migrations applied because push: false will not auto-sync the schema.