HALOZER WhatsApp Web Service v36

IMPORTANT:
- Keep the existing .wwebjs_auth folder. Do NOT delete it; it contains the saved WhatsApp session.
- Deploy only after stopping the current wa.manage.halozer.in Node app.
- After replacing server.js/package.json, run NPM Install once so the exact package versions are used.
- Start the wa.manage.halozer.in Node app.
- Open /qr and wait. If QR appears, scan it. If the existing session is valid, it should authenticate without a new QR.

Why v36:
- Reconciled v30-v35.2.
- v34 was the last version that successfully generated/scanned a QR on this hosting account.
- v35 removed Chromium's --single-process and --no-zygote flags. After that change the cPanel process count jumped toward 98/100.
- v36 restores the v34 process-saving Chromium configuration, removes dumpio browser stderr streaming, pins dependency versions, prevents overlapping queue runs, lowers queue frequency, and adds graceful shutdown.
