WC3 webdriver coming to Selenium::Remote::Driver

[George Baugh]

1.21 has been sent to CPAN for indexing, but if you're impatient you can get it as .tar.gz on the github releases here:

https://github.com/teodesian/Selenium-Remote-Driver/releases

I've tested that most everything works in Firefox, IE11, Chrome, Edge, and Safari.
Should also be backwards compatible with selenium2 using older ffx/chrome.

I'm still seeing some anomalous failures in my employer's testsuite with some of the execute_script shims used to emulate old JSONWire behavior, or to shore up buggy behavior on existing drivers.
Please be on the lookout for behavior changes in your tests, file bugs, and I will try to fix them as soon as possible.

The direct drivers are probably still broken, in the meantime, do these to run your driver (supposing everything is in the same dir):

Firefox & Chrome: java -Dwebdriver.gecko.driver=geckodriver -Dwebdriver.chrome.driver=chromedriver -jar selenium-server-standalone-3.8.1.jar
IE & Edge: java -Dwebdriver.ie.driver=InternetExplorerDriver.exe -Dwebdriver.edge.driver=MicrosoftEdgeDriver.exe -jar selenium-server-standalone-3.8.1.jar
Safari: java -Dwebdriver.safari.driver=/usr/bin/safaridriver -jar selenium-server-standalone-3.8.1.jar

I plan to get these working again soon, and add missing Selenium::Safari and Selenium::Edge direct interfaces.

I've added some code to simplify passing extra capabilities to firefox; you can pass things like so to be honored as firefox options listed here:
https://github.com/mozilla/geckodriver#firefox-capabilities

Selenium::Remote::Driver->new( ..., extra_capabilities => {
    args => [-headless],
    log => 'trace',
});

Also, if you pass the 'profile' parameter to new(), be it the zipped/base64'd or a Selenium::Firefox::Profile object, you're covered -- it will automatically put that into the extra capabilties for you.