Problem statement

Since the typescript migration on the evergree-client, we still apply ESLint, but it's a no-op. (I suppose it's looking for .js, and there's none anymore).

Expected behavior

ESLint should either be ditched on the client side, or enabled through some intermediate tooling (there are apparently a few initiatives around this like https://github.com/eslint/typescript-eslint-parser or even https://palantir.github.io/tslint/)

I think this issue is more than trivially important since ESLint, and make lint for our case, gives a false sense of consistency preservation, when actually now ESLint is basically ignored for the client side.