🐛 Bug (eslint-plugin): [no-dual-exports] Don't report on type exports

[JoshuaKGoldberg]

Coming over from readmeio/remove-undefined-objects#128 (comment): when a file has:

• A default export of a value, such as export default function stripEmptyObjects() { }
• A named export of a type, such as export interface RemovalOptions { }

...should the readme/no-dual-exports rule still trigger?

The rule's description mentions it reports on the dual exports to help with CJS resolution. But is that just at runtime? Are there type-level reasons not to? I'm not aware of any.

Proposal: can the rule be made to ignore exports that are only in type-land (interface, type)?

[erunion]

It's been a while since we wrote this ESLint rule but I recall it being a problem for type exports as well unfortunately.