QZ-702 Rewrite and Upgrade Everything (#38)

Styles 2.0!

* Documentation that explains how to use it
* Handle deps using peerDependencies, which lets us extend them
* Separate `eslint-config-react` from `eslint-config-base`: don't extend
  one from the other. This is consistent with the ESLint community.
* Upgrade all deps
* `@quartz/eslint-config-base`:
    * Nix `jest/no-disabled-tests`: it's in `jest/recommended`
    * Nix `jest/no-focused-tests`: it's in `jest/recommended`
    * Nix `jest/no-identical-title`: it's in `jest/recommended`
    * Nix `jest/valid-expect`: it's in `jest/recommended`
* `@quartz/eslint-config-react`:
    * Extend `plugin:react/recommended` because hell yes
    * Nix `react/jsx-key`: it's in `react/recommended`
    * Nix `react/jsx-no-undef`: it's in `react/recommended`
    * Nix `react/jsx-uses-react`: it's in `react/recommended`
    * Nix `react/jsx-uses-vars`: it's in `react/recommended`
    * QZ-702 Add `react/function-component-definition` for consistency
    * Disable `react/prop-types` in TypeScript: TypeScript already
      checks prop types, and it's smarter.

Author: adamhooper

README.md

@@ -0,0 +1,96 @@
+# Linting
+
+This project contains linting templates for Quartz projects. Currently, it
+contains:
+
+- `@quartz/eslint-config-base`: Base ESLint config for JavaScript projects
+- `@quartz/eslint-config-react`: ESLint config for React projects
+- `.editorconfig`: EditorConfig for all projects
+
+## Usage
+
+### Installing in your Non-React project
+
+In your shiny-new project (or the project you're retrofitting):
+
+```
+npm install --save-dev \
+      @quartz/eslint-config-base \
+      @typescript-eslint/eslint-plugin \
+      eslint \
+      eslint-plugin-es \
+      eslint-plugin-import \
+      eslint-plugin-jest \
+      jest
+```
+
+And then use it in your ESLint config, e.g. in `.eslintrc`:
+
+```
+{
+  "extends": [
+    "@quartz/eslint-config-base"
+  ]
+}
+```
+
+### Installing in your React project
+
+Yay! More dependencies!
+
+```
+npm install --save-dev \
+      @quartz/eslint-config-react \
+      eslint-plugin-jsx-a11y \
+      eslint-plugin-react \
+      eslint-plugin-react-hooks
+```
+
+And then add this to your ESLint config, like so:
+
+```
+{
+  "extends": [
+    "@quartz/eslint-config-base",
+    "@quartz/eslint-config-react"
+  ]
+}
+```
+
+## Maintenance
+
+Versions of these libraries are published to NPM.
+
+### Testing changes before publishing
+
+To test changes locally, clone this Git repo and then install the project(s)
+locally in your project -- e.g., in your `qz-react` directory:
+
+```
+npm install --save-dev /path/to/lint/eslint-react
+```
+
+See how that affects your project code. Talk it over with the team. And then:
+
+1. Publish a new version of `@quartz/eslint-config-react`
+2. In your project, install the newly-published version (so the project doesn't
+   expect stuff in the local filesystem).
+
+### Publishing NPM modules
+
+1. Make sure you have an [NPM account](https://npmjs.com) and it has been added
+   to the `@quartz` organization.
+2. Log in to NPM: `npm login`
+3. Update the package version:
+   ```
+   cd /path/to/my-package
+   npm version [patch|minor|major]
+   ```
+4. Commit the version change.
+5. Make sure everything is correct! There is no undo!
+6. Publish the new version: `npm publish`
+7. Update the dependency in projects that use the package, e.g.:
+   ```
+   cd /path/to/my-project-that-uses-my-package
+   npm update --save-dev my-package@1.0.1
+   ```

eslint-base/index.js

@@ -64,7 +64,7 @@ module.exports = {
 			'error',
 			{
 				assertionStyle: 'never',
-			}
+			},
 		],
 
 		'@typescript-eslint/no-extra-parens': [
@@ -178,14 +178,6 @@ module.exports = {
 			},
 		],
 
-		'jest/no-disabled-tests': 'error',
-
-		'jest/no-focused-tests': 'error',
-
-		'jest/no-identical-title': 'error',
-
-		'jest/valid-expect': 'error',
-
 		'key-spacing': [
 			'error',
 			{