Add Passthrough GPU Support to Dockerized Chrome in a User-Friendly Way to thermoptic for Anti-Bot Detection

The `thermoptic` Dockerized Chrome currently uses software rendering due to the lack of GPU connectivity in the container. This is a big bot detection signal which we could do without.

Problematically I think supporting the GPU for Chrome in the container is also potentially more complex, but should be investigated as an option. Obviously nothing beats using a browser outside the container in a real environment but having this turnkey way would be nice.

Start by examining how the Dockerized Chrome environment is built and launched, then investigate whether Chrome can use passthrough GPU connectivity in that container. Done means a user-friendly, turnkey GPU option is defined and works without relying on software rendering for the containerized browser.

Written by the indexing model from the issue text.