fix(cli): pass chromedriver-path arg to webdriver

[Zidious]

We were not passing the --chromedriver-path arg value to webdriver.

Within webdriver.ts config.chromedriverPath would produce undefined even if --chromedriver-path was set which would result in using the default chrome driver and not the one set by the user.

If we add chromedriverPath to the destructured args and a user provides an invalid path we do error correctly throw the error as well as use the given Chrome driver:

Invalid Path:

Valid Path:

Note: --chromedriver-path does not seem to support backwards compatibility in terms of Chrome Driver, it depends on your personal Chrome version. Example, if you're using V96 you cannot use V95 chrome driver, otherwise you will get a session error (as shown in the issue referenced).

Closes issue: #370

[michael-siek]

We should add a test for this.

[Zidious]

We should add a test for this.

I've added a test for checking when the driver path does not exist. I am not sure if we can test if the driver path does exist and run CLI. would require us to have a Chrome driver executable somewhere.