[internal] Lint typescript, json, new eslint rules

[kuceb]

Part of #2690

the best way to view this PR diff is this filter: https://github.com/cypress-io/cypress/pull/4449/files?file-filters%5B%5D=.json&file-filters%5B%5D=.md&file-filters%5B%5D=.yml&file-filters%5B%5D=dotfile&owned-by%5B%5D=
everything besides that is result of linting

motivation:
with typescript coming in, we need a way to lint it locally, in editor, and in ci. I wanted to use keep using eslint --fix, so we use @ typescript-eslint

changes:

• all the changes as a result of actually linting everything we want
• root-level .eslintignore that covers entire monorepo. This is good for editor integration (you'll get red squiggles when you need them, and won't when you don't) and running one eslint command from the root
• removes subpackages lint commands as the root now lints everything recursively (not the case for coffeelint since it has no ignore file)
• removes the need for prettier and tslint (expect for cli/types which requires tslint for dtslint)
• lints and auto-fixes .json or .eslintrc files, sorts package.json, with https://github.com/cypress-io/eslint-plugin-json
• use lint-staged properly to auto-fix partially staged files

tasks:

• remove duplicate rules from .eslintrc that are in cypress-dev/general eslint rules

• merge blankline after multiline expression eslint-plugin-dev#10 to modify eslint rule, release new version

• update source files with lint changes from blankline after multiline expression eslint-plugin-dev#10

• use @cypress/eslint-plugin-json to enfore json style across project

• lint all json

• rename cypress-dev eslint plugin to @cypress/dev

• add rule for allowing implicit braces only if oneline

• wait for new version of @cypress/eslint-plugin-dev to release

• add .vscode workspace settings for easier vscode setup

[kuceb]

formatted with default vscode JSON formatter

[brian-mann]

let's add a new scripts/eslint-verify-and-fix.js and hook it into circle and npm that both verifies and attempts to --fix.

What this is solving is situations where our base .eslintrc rules change - but then on forked PR's that have diverge - those get "missed".

We want to error during the linting stage, but we also want to provide a really good error message telling the author exactly what went wrong and how to fix it locally and push changes.

IDEA: rather than let the user do this, we could alternatively just use a cypress-bot to automatically push these fixes if we're on a PR.

[brian-mann]

Other areas worth exploring...

• sorting package.json pre-commit or pre-push
• sorting npm require or imports

Worth verifying...

• what happens on precommit hooks when there are staged files but only certain lines of the file staged?

[brian-mann]

Also let's...

• Add a JSON beautifier plugin to eslint. Something like https://github.com/lydell/json-stringify-pretty-compact or https://github.com/AitoDotAI/json-stringify-pretty-compact
• Create another plugin that allows implicit returns (and no curly braces) but only if it's a single line, not multiline. (until we do this, please add back in the eslint rule you removed)

[brian-mann]

@bkucera can we disable sourcemaps when building cypress for prod - per our last discussion? That way the eval sourcemaps only affect development.

[brian-mann]

This PR is accidentally(?) reverting work done in develop such as changes to the cli/schema/cypress.schema.json found here: https://github.com/cypress-io/cypress/pull/4449/files#diff-4e080e63eb738f2552ed87596970c631

The PR went in a few days ago here: #4300

Why is this happening? What other PR's is this PR overriding?

[kuceb]

@brian-mann my mistake. when i went to re-lint all the files, I git reset to origin/develop without merging it first, then assumed the json files were up to date with develop.

Fixed now

[kuceb]

wow, appveyor.yml thought i was trying to background a process with the '&' in my commit message.
Fixed now

[cypress-bot]

Released in 3.4.1.