chore: fix all linting issues and optimize components

lint_output_after_fixes.txt

@@ -0,0 +1,65 @@
+
+> klz-cables-nextjs@1.0.0 lint /Users/marcmintel/Projects/klz-2026
+> eslint .
+
+
+/Users/marcmintel/Projects/klz-2026/app/[locale]/layout.tsx
+  81:12  warning  '_e' is defined but never used  @typescript-eslint/no-unused-vars
+
+/Users/marcmintel/Projects/klz-2026/app/[locale]/page.tsx
+  70:12  warning  '_err' is defined but never used  @typescript-eslint/no-unused-vars
+  74:14  warning  '_e' is defined but never used    @typescript-eslint/no-unused-vars
+
+/Users/marcmintel/Projects/klz-2026/app/errors/api/relay/route.ts
+  28:11  warning  '_header' is assigned a value but never used  @typescript-eslint/no-unused-vars
+
+/Users/marcmintel/Projects/klz-2026/components/CMSConnectivityNotice.tsx
+   8:10  warning  '_status' is assigned a value but never used  @typescript-eslint/no-unused-vars
+  35:16  warning  '_err' is defined but never used              @typescript-eslint/no-unused-vars
+
+/Users/marcmintel/Projects/klz-2026/components/Lightbox.tsx
+  24:5   warning  Error: Calling setState synchronously within an effect can trigger cascading renders
+
+Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
+* Update external systems with the latest state from React.
+* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
+
+Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
+
+/Users/marcmintel/Projects/klz-2026/components/Lightbox.tsx:24:5
+  22 |
+  23 |   useEffect(() => {
+> 24 |     setMounted(true);
+     |     ^^^^^^^^^^ Avoid calling setState() directly within an effect
+  25 |     return () => setMounted(false);
+  26 |   }, []); // eslint-disable-line react-hooks/set-state-in-effect
+  27 |                                                                                                                      react-hooks/set-state-in-effect
+  26:11  warning  Unused eslint-disable directive (no problems were reported from 'react-hooks/set-state-in-effect')
+  62:9   warning  Error: Calling setState synchronously within an effect can trigger cascading renders
+
+Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
+* Update external systems with the latest state from React.
+* Subscribe for updates from some external system, calling setState in a callback function when external state changes.
+
+Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).
+
+/Users/marcmintel/Projects/klz-2026/components/Lightbox.tsx:62:9
+  60 |       const index = parseInt(photoParam, 10);
+  61 |       if (!isNaN(index) && index >= 0 && index < images.length) {
+> 62 |         setCurrentIndex(index);
+     |         ^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
+  63 |       }
+  64 |     }
+  65 |   }, [searchParams, images.length]); // eslint-disable-line react-hooks/set-state-in-effect  react-hooks/set-state-in-effect
+  65:38  warning  Unused eslint-disable directive (no problems were reported from 'react-hooks/set-state-in-effect')
+
+/Users/marcmintel/Projects/klz-2026/components/home/GallerySection.tsx
+  3:17  warning  'useState' is defined but never used   @typescript-eslint/no-unused-vars
+  3:27  warning  'useEffect' is defined but never used  @typescript-eslint/no-unused-vars
+
+/Users/marcmintel/Projects/klz-2026/middleware.ts
+  33:12  warning  '_publicHostname' is assigned a value but never used  @typescript-eslint/no-unused-vars
+
+✖ 13 problems (0 errors, 13 warnings)
+  0 errors and 2 warnings potentially fixable with the `--fix` option.
+