Trying to resolve or register 'metadata' like typing.Annotated should be an error

[Zac-HD]

Based on the typing module docs, here's a list of 'metadata types'. We should raise an explicit error if the user attempts to register or resolve them.

• Annotated - Resolves strategies from Annotated type #3082 handled the cases where we want to resolve it; but we still need to ban registering it or attempting to resolve bare Annotated
• ClassVar
• Final
• TypeAlias
• Concatenate and ParamSpec can never be registered or resolved
  • and the Callable resolver should give a specific error message if it sees these types
• TypeGuard can never be registered, returns st.booleans() for any inner type.
  • resolving a callable with a TypeGuard return annotation should be an explicit error (per the PEP and because we can't actually produce such callables)
• Self type (ban)
• Never (like NoReturn)
• TypeVarTuple
• Unpack
• LiteralString can be banned for now; we can revisit later.
• Required and NotRequired (ban registration, resolve as inner type or error if bare). They are already implemented in typing_extensions and mypy

(replaces #2978 to omit rambling discussion while we worked out what to do)

[Cheukting]

I will first add all the types that we straightly ban if having no args in the NON_RUNTIME_TYPES then will look at the individual ones seperately.

[Cheukting]

The only task that #3331 does not cover is the resolver for Required and NotRequired

[Zac-HD]

Opened a new issue just for that remaining task, since it's quite different to banning the unresolvable types 👍

Thanks again Cheuk!