Redirect developers to use Chrome for Testing buildpack

[mars]

Some developers may use Chrome without Chromedriver, but for all the others, redirect them to the Chrome for Testing buildpack that installs matching versions of Chrome + Chromedriver.

See the rendered README.

[edmorley]

Could you also update bin/compile to emit a build log warning?

[edmorley]

Could you also update bin/compile to emit a build log warning?

Oh sorry thought I was commenting on heroku/heroku-buildpack-chromedriver#66

I suppose for this repo a warning in the build log might be too much, given that you say there may be some people who aren't using Chrome with selenium etc?

That said, might Chrome for Testing still more appropriate for non-selenium use-cases too? It feels like the new buildpack uses a more sustainable approach in general (that doesn't have to install lots of transitive library deps; I presume because Chrome for Testing is statically linked?), and it would be good to not have to maintain two buildpacks.

[mars]

@edmorley Chrome for Testing still requires installation of many dependencies.

I really don't know everyway this Chrome-only buildpack could be used, and it has some nuanced aspects of wrapping the executable, which the Chrome for Testing buildpack does not do. I am doing my best to make progress to solve the Chromedriver compatibility problem, and completely sunsetting this Chrome-only buildpack feels out-of-scope.

[edmorley]

Chrome for Testing still requires installation of many dependencies.

Oh sorry since that was in a separate script, I didn't see a list of packages when I skim-read bin/compile very briefly earlier.