Add “no any” lint rule

[kriskowal]

TypeScript added the unknown to fix some liberties that are allowed with the any type that can result in runtime errors. I think this was allowing access of properties of null, for example.

Valid uses of any are vanishingly unlikely. We have some consensus to require a rationale in review. Let’s go farther and add a lint rule. There appear to be plugins we can try.

https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/no-explicit-any.md

[dckc]

Oh nice... I didn't realize tool support was feasible.

[dckc]

I just wrestled with this for half an hour or so in the nat package and couldn't get it to work.

It looks like the typescript-eslint doesn't check jsdoc.

see also jsdoctypeparser/jsdoctypeparser#50

[michaelfig]

Ideally, we would turn on stricter checking in the eslint-config package. See Agoric/agoric-sdk#3916.