nodePackages.clean-css: rename to clean-css-cli

[doronbehar]

Motivation for this change

Fix #82527 . (cc @justinlovinger ).

Things done

• Followed https://nixos.org/nixpkgs/manual/#node.js - used git add -p to add only relevant updates.

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

[doronbehar]

I got 2 PRs' commits mixed, the current set of commits should be relevant only for clean-css-cli now.

[justinlovinger]

All files look good to me :)

[prusnak]

Please rework your PR. It now has a merge conflict after PR #89184 has been merged

[doronbehar]

Fixed merged conflicts.

[doronbehar]

@GrahamcOfBorg build nodePackages.clean-css-cli

[nixos-discourse]

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/prs-in-distress/3604/25

[veprbl]

We likely may need to do something with base64 hashes (e.g. apply #89520). Meanwhile, I think, the PR could stick to changing node-packages.json file only.

[doronbehar]

@veprbl how often does someone run ./generate.sh for the node package set?

[veprbl]

Landed as 9a47504

@veprbl how often does someone run ./generate.sh for the node package set?

If you are asking for a suggestions, I'm not sure what to tell you. While I was applying this PR and another one, some other upstream dependencies had already been bumped. The way it is now, any PR that regenerates node-packages.nix will pick up irrelevant changes that would always lead to merge conflicts. Perhaps, it would work a bit more predictably if node2nix could fetch some specific snapshot of the npm registry.