Configure Puppeteer to disable sandbox in int-tests

[zhihaodev]

Fixing the test failure https://github.com/linkedin/parseq/actions/runs/16248619106/job/45969479479?pr=352 due to:

file:///home/runner/work/parseq/parseq/subprojects/parseq-tracevis/node_modules/@puppeteer/browsers/lib/esm/launch.js:268
                reject(new Error([
                       ^

Error: Failed to launch the browser process!
[3954:3954:0715/001216.732101:FATAL:zygote_host_impl_linux.cc(127)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
[0715/001216.741087:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[0715/001216.741126:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)

Disabling sandbox in int-tests as it should be safe in CI like GitHub Actions.