Fix caching of chromedriver in start_chrome(...)

Since release 3.2.4, start_chrome(...) always used to download chromedriver again.

Fix error when starting Chrome

The error was

get_chrome_driver.exceptions.VersionError: Unable to find a ChromeDriver version for the installed Chrome version

It was caused by our dependency for webdriver management not supporting current Chrome versions.

The drawback is that the new webdriver management solution doesn't cache properly. See SergeyPirogov/webdriver_manager#582.

Fix: find_all() sometimes returned elements twice

This could happen when iframes were involved and changed during Helium's search process.

Fix an error in start_chrome

There was an error when no compatible chromedriver was on PATH.

Download chromedriver automatically

Previous releases of Helium shipped with the chromedriver binaries, which are necessary for starting and controlling Chrome. But these binaries got outdated very quickly. This release switches to an approach that automatically downloads a matching chromedriver when none is installed on the system.

Kudos to @zaironjacobs for the nice library that makes this possible.

Fix urllib3 error

start_chrome(...) failed with the following error:

ValueError: Timeout value connect was <object object at 0x...>, but it must be an int, float or None.

This happened because Selenium 3 depends on urllib3, but is incompatible with urllib3 >= 2.

Add `profile` to start_firefox(...)

Thank you @a-l-e-c for the PR!

Add `maximize` and `capabilities` to start_chrome(...)

These options let you start the Chrome window maximized, or pass a DesiredCapabilities object for further customizations.

Thank you @tarunjarvis5 and @petrisorionel for the PRs!

Fix StaleElementReferenceException

This exception spuriously occurred in some automation scripts.

Update to ChromeDriver 89.0.4389.23

Thanks @avinashtechlvr for the PR!