fix: docker should install chromium and puppeteer should be no sandbox

[AidanTilgner]

A couple of considerations here:

• 1. --no-sandbox means that puppeteer and chromium won't execute in a sandbox. This could theoretically have security implications, but since this is in a docker image I doubt it will matter. Maybe something to discuss further.
• 2. I'm not entirely sure the context around ENV PUPPETEER_SKIP_DOWNLOAD=true in the Dockerfile, although based on this pr it seems that the default install script was causing an error. I'm not seeing this error during build time here, and my thinking is through the Dockerfile there's more control anyway.

[AidanTilgner]

Also for consideration, the headless: "new" thing, I added to silence the current warning about the default headless mode switching in the future.

[HenryHengZJ]

@chungyau97 have you tried root Dockerfile, not the one inside docker folder

[chungyau97]

@chungyau97 have you tried root Dockerfile, not the one inside docker folder

@HenryHengZJ I copy the changes and use it in the root folder
I test it here in my fork

[chungyau97]

Results:
Docker Folder
Before

After
Not able to test because, RUN npm install -g flowise is not using the changes of this puppeteer

Render
Before

After