This environment variable tells `node-chromedriver` to check the version
of `chrome` and install a matching version of `chromedriver`. This also
means that `chrome` must be installed before `node-chromedriver`, so
I've rearranged the steps in `setup` and `build-test-no-cache` to ensure
that. Installing a system-wide `chromedriver` with `browser-tools` is
not necessary when using `node-chromedriver` since the system-wide copy
gets ignored.

Unit tests currently fail on Node 16+ because of a problem with
scratch-audio. Once that's fixed, we should change this to use
`cimg/node:lts-browsers` instead.

use node 12 instead of 10
circleCI use browser-tools orb to install chrome and update chromedriver

Co-authored-by: Ray Schamp <rschamp@users.noreply.github.com>

Co-authored-by: Ray Schamp <rschamp@users.noreply.github.com>

Co-authored-by: Ray Schamp <rschamp@users.noreply.github.com>

This reverts commit 915afd62.

Revert "circleci stop using legacy docker images"

This reverts commit ed76988d.

Revert "circleci change how npm ci is run"

This reverts commit e170537b.

Revert "update package-lock"

This reverts commit 8a7859d5.

Revert "circle config run ci in same command as lint"

This reverts commit 21c149b7.

This is just copying over config from previous dependency managers.

Hoping this fixes the build problems I'm seeing after updating chromedriver. Lint is failing which seems odd...

actually make it a regex.

Co-authored-by: Ray Schamp <rschamp@users.noreply.github.com>

Fix logic for when to run gh-deploys. We don't want to do it for dependabot branches or pull requests.

I found this strategy suggested in 
https://discuss.circleci.com/t/create-separate-steps-jobs-for-pr-forks-versus-branches/13419