Add option to remove strict chrome version compatibility checks

[NullVoxPopuli]

My builds over at https://github.com/NullVoxPopuli/emberclear/pulls started failing due to a chrome-driver mismatch.

Can I ignore the error? or.. what needs to happen to be a little more flexible with chrome versions? (maybe I need to pin the chrome version, but I worry about that becoming stale (side project, minimal effort, etc))

[NullVoxPopuli]

Based on this: https://github.com/giggio/node-chromedriver/blob/master/README.md#custom-binaries-url

I wonder if I should force a new install of chrome driver each run and somehow ignore the bundled one?

[NullVoxPopuli]

Or maybe I could use selenium instead of browser specific drivers? https://github.com/giggio/node-chromedriver/blob/master/README.md#running-with-selenium-webdriver

Hmm