New rule: no-interfaces

[MaxDac]

Suggestion

The new rule would forbid defining interfaces in favour of types. The reason behind this rule would be to avoid the existence of two language features that offer almost the same functionality. The rule would suggest the usage of types instead.

I created an implementation example in this fork if that can be useful.

[RebeccaStevens]

We used to have this rule but we deprecated it back in v3.2.2 and removed it in v4.0.0.

We did this simply because there now exists @typescript-eslint/consistent-type-definitions which does this behavior.

[MaxDac]

Apologies, I didn't notice it when I searched for a similar rule, that's exactly what I needed, thanks for the explanation!