PYI024 is noisy

[jaraco]

This rule turns out to be noisy (PYI024 in particular). It requires re-writing all namedtuples to typing.NamedTuples and can't be fixed mechanically.

Originally posted by @jaraco in #160 (comment)

[jaraco]

I've only spot-checked a few repos, and already I've encountered three instances of this check failing.

I'm not sure the check should be disabled, but it sure is inconvenient to have it right now.

[Avasam]

This check in particular aims for typed code (function-based namedtuples can't have their attributes typed). Given there's a lot of skeleton-based projects that can only afford very basic type-checking, or doesn't even pass basic mypy yet. It would make sense to leave changing collection.namedtuple to typing.NameTuple based on usage (meaning when typed code encounters an untyped namedtuple), rather than on definition ahead of time.

That would be my reasoning for disabling PYI024 at the skeleton level.

That being said, I wonder if it could suggest an autofix where the attributes are typed as Any.

[Avasam]

idk if mypy reports it, but pyright does with reportUntypedNamedTuple. So there's already some overlap with type checkers there.