v4.1.0

• Add support for msedgedriver (issue #93)
• Allow users to provide a custom binary path via WD_CHROME_PATH and WD_EDGE_CHROME_ATH environment variables (issues #137 and #93)
• Fix a bug where the user given Chrome binary path via Selenium::WebDriver::Chrome.path was not properly escaped (issue #139)
• Fix miscellaneous code warnings.
  * Announcement: As of 06/21/2019, heroku-buildpack-google-chrome no longer requires a workaround to work with this gem. See heroku-buildpack-google-chrome#73
  for more information. The workaround now is to tell the gem where Chrome is installed on Heroku. See wiki.