Resolver improvements in next minor or major version #1756

Extracted from #1753

• Auto-enable experimentalResolver in a few situations:

  • when using ESM
  • when using nodenext / node16
  • in next major, enable by default always?

• Ensure experimentalResolver can be explicitly disabled via tsconfig.json.

• rename experimentalResolver to resolver

  • continue to parse experimentalResolver for backwards-compat

• Ensure new resolver works with yarn pnp

  • I have notes in development-docs. We can detect PNP API in runtime and call out to it only for certain specifiers

• Auto-enable esm in CLI?