Pin chromedriver version to avoid random test failures
Problem/Motivation
It appears that some of the selenium/chromedriver versions are more prone to random errors.
Core is pinning a specific version of the driver and they update it "manually", like in #3471113: Update to selenium/standalone-chrome:134 (and related issues).
The templates are using the latest version, as seen in this line.
Steps to reproduce
If you are getting random errors, maybe you are affected by this.
Proposed resolution
Decide whether we should pin the version to match core's.
Core is currently on version 127, but hoping to jump to 134.
Related issue: Issue #3471113
Related issue: Issue #3514999
Edited by drupalbot