New mac64 chromedriver binary names lead to wrong binary being installed

[JeffreyBLewis]

Operating System

mac64 (intel)

Please describe Expected behaviour

wdman:::chrome_check(verbose=TRUE) should lead to the download of
chromedriver_mac64.zip and to the installation of the correct chromedriver binary.

Please describe Actual behaviour

wdman:::chrome_check(verbose=TRUE) now results in the download of both chromedriver_mac64.zip
and chromedriver_mac64_m1.zip. This, in turn, results in the installation of the chromedriver binary from chromedriver_mac64_m1.zip which does not run on intel-based macs (raising the error "java.io.IOException: Cannot run program" error when attempting to launch selenium). This problem is the result of the introduction of new binaries for Apple's M1 processor on https://www.googleapis.com/storage/v1/b/chromedriver/.

In order to make a proper fix one would need to know what the platform/architecture name for machines with the M1 chip is, which I don't, and then to make the necessary corrections to the regexs that determine which chromedriver zip files are downloaded.

In the meantime, I was able to get wdman::selenium (and, thus, Rselenium) to work by manually removing the *-m1.zip and then unzipping the *-mac64.zip found in ~/Library/Application Support/binman_chromedriver/mac64/VERSION_NUMBER/ thus putting in place the correct chromedriver binary for an Intel mac (and then, of course, being sure to set check=FALSE when running wdman::selenium(check=FALSE) or RSelenium::rsDriver(check=FALSE) so as not to overwrite my manual fix).

Steps to reproduce the behaviour

Executing,
wdman:::chrome_check(verbose=TRUE) on an intel-based mac64 computer.

[juyeongkim]

@JeffreyBLewis Thanks. Merged your PR.