[question] what about just packaging chromedriver?

Thanks for this, I'm glad it is here... and might use it to test some stuff like https://github.com/conda-forge/staged-recipes/pull/5735 !

I imagine the build chain to build chromedriver is a bit of a bear... however, might we not (also) package the [chromedriver binaries](https://chromedriver.storage.googleapis.com/index.html?path=2.38/) themselves rather than downloading them at use time? Especially for testing, it's nice to have all your dependencies cached, and this would require a special case for, e.g. travis.