Added noSandbox option

[aaron-rai]

When running this tool from GitHub Actions it resulted in the following error frequently:

Error: Failed to launch the browser process!
[2133:2133:0923/225221.604960:FATAL:zygote_host_impl_linux.cc(128)] No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces with AppArmor, see https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md. Otherwise see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the (older) SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
[0923/225221.612352:ERROR:file_io_posix.cc(145)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[0923/225221.612406:ERROR:file_io_posix.cc(145)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
TROUBLESHOOTING: https://pptr.dev/troubleshooting
    at ChildProcess.onClose (/opt/hostedtoolcache/node/20.19.5/x64/lib/node_modules/docusaurus-to-pdf/node_modules/@puppeteer/browsers/lib/cjs/launch.js:314:24)
    at ChildProcess.emit (node:events:536:35)
    at ChildProcess._handle.onexit (node:internal/child_process:293:12)
Node.js v20.19.5

Im not sure if this change is really necessary but I added the option to set it to True and updated the readme with security considerations