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

Step toward GUI migration to circle. Have circle deploy to npm (via the circlelatest tag) and github pages.

Turning off github pages deploy in travis.

- update to node 10
- set maxWorkers on unittests so they don't spawn so many that we run 
out of memory.
- set runInBand on integration tests. There's a weird interaction that 
makes the constumes test or tutorials test fail due to a page crash.

While CircleCI is running in parallel with Travis, let Travis continue to handle the deployments.

The requirements for npm publishing and gh-pages are different anyway.

The equivalent config for Travis is only 87 lines long, and easy to read. Can CircleCI be similarly easy to read? Is this easy? Are you still reading this?