build: update ghcr.io/puppeteer/puppeteer docker tag to v24.40.0

[angular-robot]

This PR contains the following updates:

Package	Type	Update	Change
ghcr.io/puppeteer/puppeteer	final	minor	24.39.1 → 24.40.0

---

• If you want to rebase/retry this PR, check this box

---

Release Notes

puppeteer/puppeteer (ghcr.io/puppeteer/puppeteer)

v24.40.0

♻️ Chores

• puppeteer: Synchronize puppeteer versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • puppeteer-core bumped from 24.39.1 to 24.40.0

🎉 Features

• support PUPPETEER_DANGEROUS_NO_SANDBOX environment variable (#​14756) (2a8276e)

🛠️ Fixes

• roll to Chrome 146.0.7680.153 (#​14787) (443e87f)
• roll to Chrome 146.0.7680.80 (#​14778) (14685a0)

[gemini-code-assist]

Code Review

This PR updates the Puppeteer base image in the Dockerfile. My review includes a comment pointing out that this change is part of a larger process. For the update to take effect, the Docker image needs to be rebuilt and pushed, and the image digest in bazel/remote-execution/BUILD.bazel must be updated accordingly.

[gemini-code-assist]

This update to the base image is a necessary first step, but it's incomplete on its own. The remote build execution platform uses a pre-built image whose digest is pinned in bazel/remote-execution/BUILD.bazel. For this change to have any effect, the following steps are required:

1. Rebuild this Docker image.
2. Push the new image to the artifact registry (us-west2-docker.pkg.dev/...).
3. Update the container-image sha256 digest in bazel/remote-execution/BUILD.bazel.

Without these follow-up actions, the remote builds will continue to use the old image, and this update will be ineffective.