fix: use browser-actions/setup-chrome for Puppeteer in CI

Replaced manual apt-get install with official setup-chrome action.

Changes:
- Set PUPPETEER_SKIP_DOWNLOAD=true during npm ci (saves time/bandwidth)
- Use browser-actions/setup-chrome@latest to install stable Chrome
- Set PUPPETEER_EXECUTABLE_PATH env var for prerender script
- Updated prerender.js to use executablePath from env if available

This avoids package installation failures and uses the GitHub Actions
recommended approach for browser testing.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: raifdmueller

.github/workflows/deploy.yml

@@ -27,25 +27,18 @@ jobs:
           node-version: 20
           cache: npm
 
-      - name: Install Chromium dependencies for Puppeteer
-        run: |
-          sudo apt-get update
-          sudo apt-get install -y \
-            libnss3 \
-            libatk1.0-0 \
-            libatk-bridge2.0-0 \
-            libcups2 \
-            libdrm2 \
-            libxkbcommon0 \
-            libxcomposite1 \
-            libxdamage1 \
-            libxfixes3 \
-            libxrandr2 \
-            libgbm1 \
-            libasound2
-
       - name: Install dependencies
         run: npm ci
+        env:
+          PUPPETEER_SKIP_DOWNLOAD: true
+
+      - name: Setup Chrome for Puppeteer
+        uses: browser-actions/setup-chrome@latest
+        with:
+          chrome-version: stable
+
+      - name: Set Puppeteer executable path
+        run: echo "PUPPETEER_EXECUTABLE_PATH=$(which google-chrome-stable)" >> $GITHUB_ENV
 
       - name: Detect base path
         id: base

scripts/prerender.js

@@ -33,6 +33,7 @@ async function prerender() {
   const browser = await puppeteer.launch({
     headless: true,
     args: ["--no-sandbox", "--disable-setuid-sandbox"],
+    executablePath: process.env.PUPPETEER_EXECUTABLE_PATH || undefined,
   });
 
   const page = await browser.newPage();