Optimize constructing type nodes from types

Originally posted by @weswigham in https://github.com/microsoft/TypeScript/issues/34119#issuecomment-545640573

Yep, looking at the traces I see pretty much all the time spent in trySymbolTable and getAliasForSymbolInContainer, which are workers user for calculating visible symbol chains. The whole process is uncached and quite naive right now (it's pretty much the same as it was since TS 1.8, but we rely on it more and more). It has been on my backlog as something that needs to be rewritten with a better more cacheable structure for perf.

There's also a fair chunk of time spent in GC and in path component-related operations that might also need some optimization - I'm guessing the large number of import types we manufacture require a large number of path calculations which end up making a lot of garbage - some caching may be in order here.

Empieza perfilando el trabajo con símbolos visibles en trySymbolTable y getAliasForSymbolInContainer; después, investiga los cálculos de rutas de tipos de importación y la recolección de basura mencionados en el issue. Se considera terminado cuando la ruta de construcción es mediblemente más rápida y se conserva el comportamiento relevante, pero el issue no indica qué archivos ni qué pruebas ejecutar.