ESLint Plugin: Update rules for improved Prettier / TypeScript compatibility

[aduth]

In order to avoid conflicts and redundancy, this pull request updates a number of rules to either (a) disable a stylistic rule which would be redundant with Prettier formatting, and (b) reduce conflicts with TypeScript syntax specifics, where the TypeScript ESLint plugin offers enhancements to the base rule.

In theory, this could also help speed up linting, since it's running fewer rule checks.

Method:

1. Print effective configuration
   • yarn eslint --print-config .eslintrc
2. Find base ESLint enforced rules
   • console.log(JSON.stringify(Object.entries(c.rules).filter(([k,v]) => v === 'error' || v[0] === 'error').filter(([k])=> !k.includes('/')).map(([k])=>k).sort(),null,2))
3. Discover TypeScript rule enhancements
   • Search "extends the base"
4. Discover stylistic rules
   • Search "styl" or "spac" in list of enforced rules, and otherwise just manually review list of rules
5. For TypeScript overrides, retain original rule configuration of rule being overridden (refer to configuration from Step 1)

[zachmargolis]

LGTM! would it be worth committing scripts those JS blurbs as scripts so we could simplify running them for a future round of these changes?

[aduth]

would it be worth committing scripts those JS blurbs as scripts so we could simplify running them for a future round of these changes?

Listing them the way I did might give a false impression that it's more automatable than it actually is, since it did still require a fair bit of manual review, particularly in determining which are "stylistic" rules and which TypeScript plugin rules extend a base rule.

Not to say it couldn't be done, but it's probably more effort and less reliable than the value it might provide.