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

Start by investigating existing tsconfig.json files targeting esXXXX without an explicit or implied resolution strategy. Compare the downstream effects and potential breakage of changing the default from Classic to Node, then determine whether implementation is appropriate. Done means a supported decision and, if approved, the default behavior is implemented.