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.

Inizia profilando il lavoro sui simboli visibili in trySymbolTable e getAliasForSymbolInContainer, quindi esamina i calcoli dei percorsi dei tipi di importazione e la garbage collection menzionati nell’issue. Il lavoro è completato quando il percorso di costruzione è misurabilmente più veloce, preservando il comportamento rilevante, ma l’issue non indica quali file o test eseguire.