[REQ][typescript-node] Migrate to a different Node.js HTTP client

Is your feature request related to a problem? Please describe.

request, the HTTP client used in the typescript-node has been deprecated recently: request/request#3142
There's no rush here, since request will continue working.

Describe the solution you'd like

A new module should be picked, or implementation changed to use the core HTTP module. Additionally, I think the transition would be the smoothest if we introduced the new module along-side typescript-node, and switched them around once we're confident the new one is stable.

Describe alternatives you've considered

The alternative to this work is to, well, not do it. Folks can continue using typescript-node until something breaks request, use typescript-axios, hack typescript-fetch to work on node, etc.

If we decide to migrate, alternatives are:

• Change implementation to use the core HTTP module - meh
• Use another popular and well-understood module:
  • got
  • needle
  • superagent
  • ...

In my opinion, got has the API that is most similar to the one we expose right now.

Additional context

I would be willing to work on this change (I'm an active user of said generator), given maintainers' and community buy-in.

Start at the typescript-node generator and inventory how it currently uses the deprecated request client and what HTTP behavior its generated clients expose. Compare got, needle, superagent, and the core HTTP module, then define a migration path that can run alongside typescript-node before switching implementations. Done means maintainers have selected an alternative and the generator and its validation cover the replacement without breaking the existing client API.