[EPIC] Diagnostics, warnings

[cspotcode]

An epic to track diagnostic logging, warnings, and tools users can use to better understand what's happening.

The goal is for users to diagnose their own problems and walk away from the experience with a better understanding of ts-node rather than frustration.

• Known problematic tsconfigs
  • Log warning when "target" is too high for the node version #1248
  • Error when tsconfig.compilerOptions.module is unsupported by Node #1069
  • Warn on noEmitHelpers: true because is likely to cause problems; causes unhelpful error #1691
  • Warn to enable resolver when using node12/node16/nodenext
  • Warn when nodenext/node16 is used with an incompatible moduleResolution mode (Concerns with TypeScript 4.5's Node 12+ ESM Support microsoft/TypeScript#46452 (comment))
• Generic warnings and hints mechanism #1445
• --explain-file and/or --explain-import, --cat-file to dump detailed information about how and why ts-node treats a file a certain way #1461
• --emitFile debug flag to emit the compiled output of a single file to stdout #1366
• Warning when TS resolver detects node builtin, yet @types/node was not resolved #1446
• Maybe copy new ERR_REQUIRE_ESM error messaging from node #1407
• Debug logging of new features #1271
• --doctor option logs advice to help with project configuration #1203
• Add diagnostic logging to ts-node #960
• When transpiled code attempts to require tslib, regenerator-runtime, or @swc/helpers, log a helpful warning about adding those dependencies; link to relevant docs page
• Link diagnostics to TSWhy #1692
• Make --showConfig moduleTypes log correct, relative paths same as include #1389
• support for traceResolution #1128
• ts-node -vvv also logs the paths to ts-node and typescript, so it's more obvious when you're accidentally using the global ones #1323