Unpin chromedriver version and use latest or highest possible version

Problem/Motivation

Up until 📌 Pin chromedriver version to avoid random test failures Active , we were using selenium/standalone-chrome:latest image for the chrome driver, which is the desired option, but in the past weeks, contrib modules were being affected but false positives failures that would go away re-running the jobs.

This is due to a change in behaviour introduced in some of the later chrome driver versions. Core pins the image to be version 127.0, and that's what we did in the previous issue. There is an issue to update to 134.0 here 📌 Update to selenium/standalone-chrome:128 Active , and ideally, if it's eventually fixed upstream, to latest again.

Proposed resolution

Either go back to latest or try to match whatever core has updated to in the related issue.