fixes #1821 by installing required drivers and adding options to chro…

[psvensson]

…medriver

Background

The web_browse functionality has been broken in the Docker container (and possibly outside it) for a day or two.
This PR adds a number of needed libraries and options when invoking the chromium webdriver which fixes the problems (see #1821 for example)

Changes

New libraries apt-got in Dockerfile + more options to the chromium creation

Documentation

Test Plan

PR Quality Checklist

• My pull request is atomic and focuses on a single change.
• I have thoroughly tested my changes with multiple different prompts.
• I have considered potential risks and mitigations for my changes.
• I have documented my changes clearly and comprehensively.
• I have not snuck in any "extra" small tweaks changes

[shahdevansh]

Works for me

[bvoo]

tested and can also confirm working

[nponeccop]

@psvensson There are lint errors now

[psvensson]

hmm OK. The only thing left in my PR is one line in the Dockerfile. Is this where the lint errors are?

[psvensson]

Ah hang on, I see it. thx

[vmajor]

Does not work for me: Command browse_website returned: Error: Message: Service /home/*****/.wdm/drivers/chromedriver/linux64/112.0.5615.49/chromedriver unexpectedly exited. Status code was: 127

[psvensson]

Does not work for me: Command browse_website returned: Error: Message: Service /home/*****/.wdm/drivers/chromedriver/linux64/112.0.5615.49/chromedriver unexpectedly exited. Status code was: 127

Are you testing in docker (just want to make sure)?

[vmajor]

No, native in WSL2 in a conda venv. chrome fails with that error, firefox fails with "user profile not found" error even though it is meant to be headless and it runs fine with a gui when started manually. I will try to run Auto-GPT under windows next.

[universeroc]

Not works for me natively run on CentOS with conda env, how to fix it? help me thanks in advance:)