Puppeteer fails to launch on ARM architecture due to incompatible Chromium binary

[fapfaff]

Describe the bug
When running Puppeteer on an ARM-based system, the application fails to launch the browser due to an incompatible Chromium binary. This results in errors like:

Logs

### 2025-01-04T10:08:58: PM2 log: Launching in no daemon mode
2025-01-04T10:08:58: PM2 log: App [index:0] starting in -fork mode-
2025-01-04T10:08:58: PM2 log: App [index:0] online
Started Fredy successfully. Ui can be accessed via http://localhost:9998
Started API service on port 9998
Error executing with puppeteer executor Error: Failed to launch the browser process!
/root/.cache/puppeteer/chrome/linux-131.0.6778.108/chrome-linux64/chrome: 1: %@@@����tεtεе����
                                                                                              ��
                                                                                                ��[�: not found
/root/.cache/puppeteer/chrome/linux-131.0.6778.108/chrome-linux64/chrome: 3: Syntax error: ")" unexpected
/root/.cache/puppeteer/chrome/linux-131.0.6778.108/chrome-linux64/chrome: 1: ELF: not found
TROUBLESHOOTING: https://pptr.dev/troubleshooting
    at Interface.onClose (/fredy/node_modules/@puppeteer/browsers/lib/cjs/launch.js:314:24)
    at Interface.emit (node:events:530:35)
    at Interface.close (node:internal/readline/interface:527:10)
    at Socket.onend (node:internal/readline/interface:253:10)
    at Socket.emit (node:events:530:35)
    at endReadableNT (node:internal/streams/readable:1698:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Cannot parse, text was empty.

To Reproduce
Steps to reproduce the behavior:

1. Install Fredy on an ARM system
2. Run a job

Expected behavior
The job should run successfully

Proposed Solution

1. Install chromium via apt
2. Configure puppeteer to stop installing the bundled chromium and use system version instead