The type-aware scan pins config/oxlint-code-quality-type-aware.json, and mobile's
types resolve only from mobile/node_modules. Every mobile import of a type that
lives there becomes an 'error' type under the root config, and
no-redundant-type-constituents then reports it as a real finding - eight of them
on this PR, none reproducible with the package script, which scopes that scan to
'src config tests' precisely because of this.
The untyped scan already documents the same hazard and avoids it by not pinning a
config at all. The type-aware scan cannot do that, so it skips mobile instead.
Brennan Benson
41e6078bb4