Using `types` classes over `collections.abc`'s bases

Currently collections.abc.Generator/Coroutine/AsyncGenerator etc. have attributes that don't have to exist at runtime. I think it'd be wise to switch recommending to using the types concrete classes where possible over the abstract versions which have a smaller interface because having this weird sort of duplication where the 2 are basically the same is a wrinkle that's bitten me recently. To do this I think a few things need to happen:

1. make the classes in collections.abc.pyi Protocols that should be based on their runtime implementation (they implement custom __subclasshook__) and not the concrete types. (https://github.com/python/typeshed/pull/10816)
2. make the types classes subscriptable at runtime. (https://github.com/python/cpython/pull/110212)
3. make type checkers infer things like def foo(): yield as types.GeneratorType and not just collections.abc.Generator.

(as a small aside it might be nice to move the type implementations from typing to collections.abc soon)

refs: https://github.com/microsoft/pyright/issues/6053

Comienza revisando las clases de collections.abc.pyi y los pull requests vinculados de typeshed y CPython. Después, examina cómo los comprobadores de tipos infieren las funciones generadoras, de coroutine y de generador asíncrono. Se considera terminado cuando los tipos abstractos y concretos presentan el comportamiento propuesto en tiempo de ejecución y de inferencia en todos los cambios identificados.