no-empty-interface: allow providing type arguments for extended type

[ajafff]

PR checklist

• Addresses an existing issue: no-empty-interface should not fail on an interface that resolves types #3256
• New feature, bugfix, or enhancement
  • Includes tests
• Documentation update

Overview of change:

[bugfix] no-empty-interface allows providing type arguments for extended type
Fixes: #3256

Is there anything you'd like reviewers to focus on?

The rule now ignores every interface whose parent has type arguments. That leads to some false-negatives:

interface Base<T> {
    prop: T;
}

interface Good extends Base<string> {}
interface Bad<T> extends Base<T> {}
interface ProbablyGood<T extends string> extends Base<T> {}
interface ProbablyGood2<T = string> extends Base<T> {}

interface Base2<T, U = void> {
    prop: T,
    prop2: U;
}

interface Bad2<T, U> extends Base2<T, U> {}
interface Good2<U, T> extends Base2<T, U> {}
interface Good3<T> extends Base2<T> {} // looks like `Bad`, but isn't ... would require the type checker

There will be no error on any of these declarations. One might expect errors on Bad and Bad2 (and maybe even on ProbablyGood, ProbablyGood2 if the base type has the same default and/or constraint) but that requires the type checker to find out about all type parameters of the base type.

I don't know if these rare cases are worth the effort. Anyways, that should be done in a separate PR.

CHANGELOG.md entry:

[adidahiya]

nice, yeah, keeping it simple here is good

[ghost]

Could this be put behind an option? I'd like to still get errors for interface T extends U<string> {} on DefinitelyTyped as this can just be type T = U<string>;.