[GCP] grafana-image-renderer is failing to start browser

[fruch]

Installation details
Panel Name:
Dashboard Name:
Scylla-Monitoring Version: 4.9.0
Scylla-Version: master (2025.2-dev)

since we move to use the GCP image of monitor for 4.9.0, we can capture screen shots on GCP

every capturing end like the following:

$ docker logs agrafrender
{"level":"info","message":"HTTP Server started, listening at http://localhost:8081"}
{"level":"error","message":"Request failed","stack":"Error: Failed to launch the browser process!\nchrome_crashpad_handler: --database is required\nTry 'chrome_crashpad_handler --help' for more information.\n[18:18:0305/064626.529099:ERROR:socket.cc(120)] recvmsg: Connection reset by peer (104)\n\n\nTROUBLESHOOTING: https://pptr.dev/troubleshooting\n\n    at Interface.onClose (/usr/src/app/node_modules/puppeteer-core/node_modules/@puppeteer/browsers/lib/cjs/launch.js:310:24)\n    at Interface.emit (node:events:529:35)\n    at Interface.close (node:internal/readline/interface:534:10)\n    at Socket.onend (node:internal/readline/interface:260:10)\n    at Socket.emit (node:events:529:35)\n    at endReadableNT (node:internal/streams/readable:1400:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)","url":"/render?deviceScaleFactor=1.000000&domain=172.17.0.1&encoding=png&height=-1&renderKey=Mj1owMBiDyNaU07DbUenUtsgio2Y1eP9&timeout=60&timezone=&url=http%3A%2F%2F172.17.0.1%3A3000%2Fd%2Foverview-master%3ForgId%3D1%26from%3D1741156798000%26to%3D1741179298000%26width%3D1600%26height%3D-1%26kiosk%26render%3D1&width=1600"}
{"level":"error","message":"::ffff:10.142.0.104 - - [05/Mar/2025:06:46:26 +0000] \"GET /render?deviceScaleFactor=1.000000&domain=172.17.0.1&encoding=png&height=-1&renderKey=Mj1owMBiDyNaU07DbUenUtsgio2Y1eP9&timeout=60&timezone=&url=http%3A%2F%2F172.17.0.1%3A3000%2Fd%2Foverview-master%3ForgId%3D1%26from%3D1741156798000%26to%3D1741179298000%26width%3D1600%26height%3D-1%26kiosk%26render%3D1&width=1600 HTTP/1.1\" 500 96 \"-\" \"Grafana/11.4.0\"\n"}

note that same version on AWS AMI works as expected

[amnonh]

Fixed by #2486