Move away from Classic module resolution as default for all module kinds

TypeScript's original module resolution strategy (the Classic resolution strategy) has some strange behavior that apparently doesn't actually reflect any other resolution strategy. It seems strange that those using non-CommonJS emit targets get this behavior by default.

Classic resolution also causes many disk probes during the walk up the project root - assuming that this strategy does eventually succeed in most cases, it seems like most uses could be subsumed by:

• Using relative paths.
• Modifying the baseUrl and paths properties in tsconfig.json.

After discussing with @vladima, we think it is worth considering switching the default resolution strategy for all module targets to Node.

Here's what needs to be done:

• Investigate existing tsconfig.jsons that target esXXXX` and have no explicit/implied resolution strategy.
• Determine the downstream effects to a change to defaults
• Determine if this change outweighs the potential breakage
• Implement if appropriate

Inizia analizzando i file tsconfig.json esistenti che hanno come target esXXXX senza una strategia di risoluzione esplicita o implicita. Confronta gli effetti downstream e i potenziali malfunzionamenti derivanti dalla modifica del valore predefinito da Classic a Node, quindi determina se sia appropriato procedere con l’implementazione. Il lavoro è considerato concluso quando è stata presa una decisione supportata e, se approvata, è stato implementato il comportamento predefinito.