Some TLC

[kevindew]

In an attempt to not fully understand why we're checking ETXTBSY issues that are breaking tests (it seems to be that we're checking Chrome version while executing) I've done some basic updates to get things up to date. I've updated all gems, removed some unnecessary node installation in the e2e docker file and fixed linting issues.

Assuming this doesn't fix the problem (I can't see a good reason it would) here are some ideas:

• we turn off parallel tests and deal with the extra time (I believe the problem is one rspec process is trying to replace the chrome binary while the other is updating it)
• we do a grim monkey patch to disable Webdrivers from updating the binary - it won't actually need updating as this is done as part of building the Docker image
• we set different chrome paths for each test worker which means they all have their own version of chrome installed so can't conflict.

All don't sound very nice. I wonder if what is happening is that we've somehow got a mismatch between chrome versions and webdriver version so we're trying to update repeatedly?

[1pretz1]

Looks good to me! 🤞

[ChrisBAshton]

LGTM too 👏 thanks Kevin!