nest-cli: repackage using buildNpmPackage

[ehllie]

Description of changes

Repackages nodePackages.@nestjs/cli to be built using buildNpmPackage as per the suggestion in #229475

Things done

Moved nest-cli to pkgs/development/tools and removed it from node-packages.json.
Had to regenerate package-lock.json after running npm upgrade to fix the build failing on Darwin.
Once #229639 gets merged I will also include it in aliases.nix that it adds.

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.05 Release Notes (or backporting 22.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[SuperSandro2000]

Please rebase and add an alias

[ehllie]

Please rebase and add an alias

I have done that, but I have an issue I pointed out here #229639 (comment). As it stands nodePackages.@nestjs/cli does not evaluate because it shadows the package in node-packages.nix, which I would like to avoid having to manually edit or re generate.

[ehllie]

I've also deleted @nestjs/cli from node-packages.nix so that the alias is not an error in case we want to stay with the current iteration of the alias file

[dotlambda]

Had to regenerate package-lock.json after running npm upgrade to fix the build failing on Darwin.

Did you ask upstream to regenerate their lock file? We cannot add 15k lines of code for every single package.