fix: verify @types/node version with registry

[molisani]

Resolves #30

Describe your changes
New behavior to check the locally-configured registry for @types/node and only write a version that exists to the package.json for the new project.

The registry URL is pulled from one of two sources:

• The NPM_CONFIG_REGISTRY environment variable
  • Less common use case, but good to read from an env var if possible
• Executes NPM_EXECPATH with process.execPath and args config get registry
  • This method works for npm, yarn, and pnpm as all of them set that environment variable and share those command line args (tested this manually)

Once the data is fetched from the registry, there is additional logic to determine if there is an exact or approximate (same major version) version of @types/node available. If not it defaults to the highest published LTS version.

Testing performed
Updated test suite to hit 100% coverage. (Also removed some outdated baselines)

[molisani]

This is a preventative change for future versions of Node.js/@types/node. As such, we hardcode a known maximum and if the version is beneath that we do not have to go through this new logic.

[mkubilayk]

As discussed offline, it might be nice to bypass this using a --node-version flag but changes look good. I like that more complicated logic only kicks in for super fresh things.