Fix how Chrome is launched for testing

[romaricpascal]

What

Fix how Chrome is launched by Karma and WebDriver.io on GitHub CI so it runs properly rather than error.

Note

We used to set the --no-sandbox and --disable-setuid-sandbox flags of Chrome in GOV.UK Frontend. While we could do this with both Karma and WebDriver.io, we've since removed the flags from GOV.UK Frontend so there might be alternative solutions.

Why

So tests run again

Who needs to work on this

Developers

Who needs to review this

Developers

Done when

• Karma tests run again on CI
• WebDriver tests run again on CI

[romaricpascal]

The fix-chrome-headless-ci branch proposes a fix using the --no-sandbox and --disable-setuid-sandbox flags, but it'd be good to find a sturdier solution. It may come from upgrading our tooling to more recent versions of Karma and Webdriver.io.

[domoscargin]

I think it's fine to use this for now to unblock us and create an issue for a more robust fix, as you suggested.