Making WebDriver less fragile with browser version changes (OSOE-359)

[Piedone]

While WebDriverManager.Net now supports Chrome version selection too we can still improve on this by e.g. bundling a browser with the project instead of relying Chrome and others to be installed on the given machine (and thus taking a hard dependency on a specific Chrome version that goes away with a random auto-update).

Some alternatives:

• Use a portable Chromium exe instead (and somebody else did this from C# too). There is no NuGet package for this, however (we could create one but there might be licensing issues, or somehow download it on the first run).
• Use Selenoid to package up browsers into Docker containers. This is abandoned now, though, and its successor is the non-OSS https://github.com/aerokube/moon.
• EO.WebBrowser is a self-contained Chromium browser engine in a NuGet package. Supposedly this can work with ChromeDriver but there might be pitfalls and it might be slower.
• Install Chrome automatically (like this unmaintained package does). This is obtrusive, however, and may not work in all environments.

Jira issue

[Piedone]

We now use Atata.WebDriverSetup. While this covers the issue of setting up the WebDriver for all major browsers, a browser should still be preinstalled.

However, this is not a big issue now, especially that any other approach would make testing slower.

[Piedone]

Browser updates can still break our tests, and this happens with GHA runner image updates all the time.

BTW Chrome for Testing can be useful (I guess it's used in the images too).

[Piedone]

This is covered by #478.