feat(eslint-plugin): add no-unsafe-any

[bradzacher]

Fixes #791

WIP

• still need to cover more cases
  • member and call expressions on an any
  • (maybe) assigning any generics to stricter ones (const x: Set<string> = new Set<any>([false]);)
  • better error messages (put in var names)
  • options for each of the check
• option for checking if variable is an exception arg (as they are always any)???
• performance
  • this rule is super slow currently (17s on our codebase).
  • need to figure out how to make it less chatty, or how to cache things. Unsure.
  • I'll need to do some profiling to see where the bottlenecks are exactly.

---

New rule which uses type information to validate that you're not doing anything with an any.

It's easy to keep your own code (mostly) safe via the no-explicit-any rule, but there are a number of places where things can get unsafe due to library types (from DefinitelyTyped, or from the default TS libraries).

This rule will help catch of those cases.

const a = Object.defineProperty({}, 'a', {}); // typeof === any

const b = new Map();
b.get('a'); // typeof === any

const c = JSON.parse('{}'); // typeof === any

const d1 = [], d2 = Array(3); // typeof === any[]

let e1 = null, e2 = undefined, e3; // typeof === any

// etc..

[typescript-eslint]

Thanks for the PR, @bradzacher!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

---

🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day.

[bradzacher]

closing in favour of the no-unsafe-* rules that I've implemented