Revert "nut: 2.7.4 -> 2.8.0"

[cyounkins]

Description of changes

The change in #215890 didn't change the sha256 so the version and hash do not match. While I'm excited to land version 2.8.0, we should revert the version number until we can get a solid PR for it.

Ofborg issue asking if we can detect this condition: NixOS/ofborg#647

This should be backported to the 23.05 branch, but I'm unsure how to do that.

@markuskowa

Things done

• 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.11 Release Notes (or backporting 23.05 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.

[markuskowa]

The preferred way is to use git revert 47cfb7f0906f3cb877aa9a9c348ca8709deec141,
to clarify it in the git history.

[cyounkins]

Yeah, that works too. I had wanted to keep the URL interpolation portion, but it's not a big deal. Should be good now.

[SuperSandro2000]

redundant with #233031