Suggest valid type forms when type(...) is called in annotations

[QEDady]

Summary

Follow-up to #5087.

In Python, built-in singleton constants and runtime objects like NotImplemented, Ellipsis, None, and modules do not expose their types as builtins, so users frequently write type(...) in type annotations (or confuse type(MyClass) with type[MyClass]).

When a single-argument call to builtins.type(...) appears in an annotation where function calls are invalid, inspect the argument type and append a helpful suggestion to the invalid-annotation error message:

• type(NotImplemented) -> Did you mean `types.NotImplementedType`?
• type(Ellipsis) / type(...) -> Did you mean `types.EllipsisType`?
• type(None) -> Did you mean `None`?
• type(some_module) -> Did you mean `types.ModuleType`?
• type(MyClass) -> Did you mean `type[MyClass]`?

Test Plan

Added test_type_call_in_annotations in pyrefly/lib/test/annotation.rs and ran cargo test.

[meta-codesync]

This pull request has been imported. If you are a Meta employee, you can view this in D123716933. (Because this pull request was imported automatically, there will not be any future comments.)

[github-actions]

According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅