fix: ignore ESLint and TypeScript errors during Next.js build

Intentional code quality violations should not block container build.
Linting is done separately by the scanner workflows.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: emmanuelknafo

cq-demo-app-001/next.config.ts

@@ -2,6 +2,12 @@ import type { NextConfig } from "next";
 
 const nextConfig: NextConfig = {
   output: "standalone",
+  eslint: {
+    ignoreDuringBuilds: true,
+  },
+  typescript: {
+    ignoreBuildErrors: true,
+  },
 };
 
 export default nextConfig;