Remove sticky selenium/chrome once it's solved upstream

[stronk7]

selenium/standalone-chrome:3.141.59-2021729 introduced some regression causing the webdriver not to connect as expected. So, we did #176 to switch to known-to-work version.

Some related links:

• Behat step fails with latest chrome selenium 3.141.59-20210729 moodle-plugin-ci#121
• Disable Chrome's GPU support in BrowserWebDriverContainer testcontainers/testcontainers-java#4315
• New standalone-chrome image: SessionNotCreatedError SeleniumHQ/docker-selenium#1351
• Underlying Chromium issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1228625

This issue is about to remove the sticky version once the problem is solved upstream or we find an alternative solution (disable-gpu seems to work too, for example).

[stronk7]

Side note: we'll have to also do moodlehq/moodle-plugin-ci#123 is a similar way.

[stronk7]

Was looking for other selenium stuff when I saw that they have already added a fix for the latest selenium images not starting properly: https://github.com/SeleniumHQ/docker-selenium/blob/selenium-3/NodeChrome/wrap_chrome_binary
(add —disable-gpu)

So maybe we can give it a try and proceed with the unpin.

[dahrens]

I've tested locally right now and it looks like you can revert the commit that pinned to the specific version.