Errors when chromedriver beta releases a new version and npm version is 2 versions behind

[straker]

There is a small window of time where Chromedriver beta gets a new release and is then 2 versions ahead of the npm version and causes the build to fail. Need to implement some sort of fallback for these scenarios as to allow tests to continue to work while the npm version plays catchup.

Chrome Beta version detected as Google Chrome 102.0.5005.27 beta
Installing ChromeDriver 102
log: Received response of 100.0.0
ChromeDriver 102 not found. Retrying with ChromeDriver 101
browser-driver-manager error: Unable to get ChromeDriver version; Something went wrong

Exited with code exit status 1

[straker]

Fixed in v2 release