we have a lot of issues with declarations, i solved some of them in #88

Trying to fix this. The code in #88 is marking Foo as used, but the rule still reports it as unused.

i think we should move this to parser as @mysticatea proposed in some old PR in eslint/typescript-eslint-parser#558

with that we could control it better, we can store information that we in "augmentation" like we do with types and override __define to mark is as used when is set

otherwise we should stop overriding eslint rule and write a little more complex logic by ourself (they have something similar for exports)

we have also false positives from #54

i just realized that #88 is leading to some false positives

var baz = 2
declare namespace Foo {
  var foo: bar.baz
}

baz is going to be marked as used

Not sure how moving the check to the parser would help as the rule is still ignoring markVariableAsUsed.

i was thinking a little to far ahead, and didn't explain it (i tend to do so)

• ResizeObserver is defined in 2 scopes class and module
• markVariableAsUsed is setting eslintUsed for variable in one scope, in this case for class scope
• scope of variable is determined by https://github.com/eslint/eslint/blob/master/lib/linter.js#L522
  const currentScope = getScope(scopeManager, currentNode);
  and we already entered class scope because Identifier is a child of ClassDeclaration
• eslint checks variable in scope module and its not marked as used
  and there is an error