Support multiple drivers for Chrome, Chrome-for-Testing, and Chrome-Headless-Shell #3861
Description
Support multiple drivers for Chrome, Chrome-for-Testing, and Chrome-Headless-Shell
It's possible that you could have different versions of regular Chrome, Chrome-for-Testing, and Chrome-Headless-Shell installed on your machine. If so, you shouldn't need to download a new chromedriver when switching between those because currently, the same chromedriver in seleniumbase/drivers is used for all of them.
SeleniumBase makes sure you have matching versions, so it will keep downloading and overriding your chromedriver when switching between Chrome, Chrome-for-Testing, and Chrome-Headless-Shell if the versions of those are different. To resolve this, there should be a different folder for each one (for holding the chromedriver). Chrome-for-Testing may also have limited support for uc_driver.
Additionally, #3859 provides a way to customize your drivers folder if you choose not to use the default location in seleniumbase/drivers.
With this ticket, there will be three default folders in total for holding drivers:
seleniumbase/driversseleniumbase/drivers/cft_driversseleniumbase/drivers/chs_drivers