[#795] Fixed lazy instantiation for some fields of WebDriverManager

[jensbac]

Purpose of changes

fix for issue #795

Types of changes

Fixed lazy instantiation for fields resolutionCache, versionDetector and webDriverCreator of WebDriverManager.

• Bug-fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How has this been tested?

New version was build locally and included to an using project.

WebDriverManager.chromiumdriver().setup() now produces the log output:

[DEBUG] Detecting chromium version using online commands.properties
[DEBUG] Running command on the shell: [chromium-browser, --version]
[DEBUG] Result: Chromium 98.0.4758.102 snap
[DEBUG] Latest version of chromedriver according to https://chromedriver.storage.googleapis.com/LATEST_RELEASE_98 is 98.0.4758.102
[INFO] Using chromedriver 98.0.4758.102 (resolved driver for Chromium 98)
[DEBUG] Found CHROMIUM snap
[INFO] Exporting webdriver.chrome.driver as /snap/bin/chromium.chromedriver

instead of downloading a chromedriver.

Notes:

• Nevertheless due to Selenium issue 7788 starting the snap installed chromedriver does not work on e.g. Ubuntu 20.04. But the workaround described there does the job.
• mvn verify executed for this fixed version continues complaining about 10 failing tests when executed on Ubuntu 20.04 with snap installed chromium and chromium.chromedriver but no installation of google-chrome (same as without the fix). These are related to WebDriverManager.chromedriver().setup() which cannot detect a google-chrome but downloads and starts a chromedriver which finally starts a chromium but cannot control it.