Getting specific chromedriver version ignores patch number

[TravkinAlex]

As partially described in #408, patch version gets ignored for chromedriver;
this has been fixed for getting LATEST version, but for getting the SPECIFIC version the issue is still relevant. relevant for both since getting latest still uses the same method
[13:04:17] I/downloader - curl -oD:\BillfoldRepos\webdriver-manager\selenium/chromedriver_76.0.3809.68.zip https://chromedriver.storage.googleapis.com/76.0.3809.12/chromedriver_win32.zip

Steps to reproduce:

1. Use webdriver-manager 12.1.7 (currently latest)
2. Run webdriver-manager update --versions.chrome=76.0.3809.68
3. Actual result - download is from URL https://chromedriver.storage.googleapis.com/76.0.3809.12/chromedriver_win32.zip, actual chromedriver downloaded is 76.0.3809.12, the binary file then gets renamed (?) to 76.0.3809.68.

I've submitted a fix in #413 .

Seems like a related issue - #401 .

[VadimSkuratovskyi]

Faced with the same issue, trying to install the latest 76 version of chromeDriver-76.0.3809.126 for the Chrome-v76 using latest webdriver-manager 12.1.7
webdriver-manager update --versions.chrome=76.0.3809.128
but downloaded --chromeDriver - v76.0.3809.12 and receiving next in console:
(\node_modules\webdriver-manager\selenium/chromedriver_76.0.3809.128.zip https://chromedriver.storage.googleapis.com/76.0.3809.12/chromedriver_win32.zip)
Could anyone please take a look at this pull request?
@cnishina I hope you can help us to fix this issue.

[captaincaius]

Doh! Sorry for the duplicated effort but I made #447 before realizing the other PR existed ...

[captaincaius]

PS technically it's not the patch number, but one level below it ;)