Associate node interpreter to TypeScript

[pchaigno]

This pull request adds the node interpreter to TypeScript to help with the recognition of TypeScript files with a .js extension.

Description

The node interpreter is already associated to JavaScript, but thanks to #4099, subsequent strategies (e.g., the Extension Strategy) can now refine the results and distinguish between TypeScript and JavaScript file.

Fixes #4112.

Checklist:

• I am fixing a misclassified language
  • I have included a new sample for the misclassified language:
    • Sample source(s):
      • https://github.com/ricardolissa/Biblioteca/blob/24f43313448abf8def285ed71e49bdc9ba7b4cb9/apibiblioteca/platforms/browser/cordova/run
      • https://github.com/BlueWaterloo/Angular/blob/7ae706d6cf61247b507b8fd48d355197f6ee78e1/packages/compiler-cli/src/main.ts
    • Sample license(s): MIT for both.
  • I have included a change to the heuristics to distinguish my language from others using the same extension.

[Alhadis]

In about five years, we'll be stuffing Perl scripts and Python runtimes directly inside JavaScript source code, and expecting some magic genie's compiler to cope with it all... 😝

[pchaigno]

...and still writing the kernel on which all this stuff runs in C.

[Alhadis]

I foresee this to be the future of kernel programming, according to current trends:

That edit also wouldn't suck so much if I still had access to Adobe software. 😓

[pchaigno]

Who want to write kernel code in Go??! I doubt we're even gonna write large pieces of kernel code in Rust before a long time...

[lildude]

LGTM