Expand documentation for integrating type stubs into existing code bases

On https://typing.readthedocs.io/en/latest/index.html there are various sections to help users find tools such as type checkers, linters and formatters, and development environments with type support.

I had previously asked in python/typeshed#8482 how would a user go about integrating existing type stubs into their application. This may be due to a third party or typeshed having created stubs either because the type hints were missing in a library or the provided type information was sufficiently inaccurate to encourage the user to take this type of action.

The team was kind enough to suggest various tools to assist with addressing this problem, and I was wondering if there was an appetite by the team here to incorporate a new "Type Stub Integration" section (or a different proposed name) to the Typing-Related Tools section?

Comienza leyendo la sección Typing-Related Tools en https://typing.readthedocs.io/en/latest/index.html y la discusión sobre la integración referenciada en python/typeshed#8482. Determina el alcance y el nombre adecuados para una sección Type Stub Integration y, a continuación, actualiza la documentación para que los usuarios puedan encontrar orientación y herramientas relevantes para integrar stubs existentes.