test(docker): drop worker cap and skip-lint OpenShift build opts

Keep filtered pnpm install and hoisted node-linker as the only
memory-related Docker changes for Azure review build testing.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: mrTuomoK

Dockerfile

@@ -140,12 +140,6 @@ USER default
 ENV HUSKY=0
 RUN pnpm install --frozen-lockfile --filter ${PROJECT}...
 RUN pnpm --filter ${PROJECT} run share-static-hardlink
-# OpenShift build pods are memory-constrained. Match GitHub CI build settings and
-# limit Next.js static-generation workers (default is 4 parallel child processes).
-ENV NEXTJS_IGNORE_ESLINT=1 \
-    NEXTJS_IGNORE_TYPECHECK=1 \
-    NEXT_BUILD_CPUS=1 \
-    NEXT_TELEMETRY_DISABLED=1
 RUN pnpm --filter ${PROJECT} run build
 
 # Does not play well with buildkit on CI

next.base.config.mjs

@@ -15,9 +15,6 @@ const trueEnv = ['true', '1', 'yes'];
 // const isProd = process.env.NODE_ENV === 'production';
 const isDevelopment = process.env.NODE_ENV === 'development';
 const isCI = trueEnv.includes(process.env?.CI ?? 'false');
-const nextBuildCpus = process.env.NEXT_BUILD_CPUS
-  ? Number(process.env.NEXT_BUILD_CPUS)
-  : undefined;
 
 const NEXTJS_IGNORE_ESLINT = trueEnv.includes(
   process.env?.NEXTJS_IGNORE_ESLINT ?? 'false'
@@ -139,9 +136,6 @@ const nextBaseConfig = ({
       // Experimental monorepo support
       externalDir: true,
       scrollRestoration: true,
-      // Limit parallel page-data workers in memory-constrained Docker/OpenShift builds.
-      ...(nextBuildCpus ? { cpus: nextBuildCpus } : {}),
-      ...(nextBuildCpus ? { webpackMemoryOptimizations: true } : {}),
     },
 
     // 🚨 TURBOPACK CONFIGURATION