Hook tsconfig "extends" resolver to resolve "ts-node/node14/tsconfig.json" to self when globally installed

Follow-up to #1202

If running the globally-installed ts-node, and tsconfig "extends" points to a "ts-node/node*/tsconfig.json", and local resolution fails:
Fallback resolve to the globally-installed ts-node

Although, in these situations, tsc will fail to resolve.  So is this really a good idea?  Need to think about it.