haskellPackages.nvfetcher: add to top-level

[berberman]

Motivation for this change

Things done

• 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/)
• Added a release notes entry if the change is major or breaking
• Fits CONTRIBUTING.md.

[cdepillabout]

@GrahamcOfBorg build nvfetcher

[cdepillabout]

This looks good, thanks for adding yourself as maintainer!

[maralorn]

Question: We lately had a trend to move overrides which actually fix packages move into configuration-common.nix. I think that would have been better in this context, too. (Concretely: Have only the justStaticExecutable on the top-level.)
Do we want to continue that? Or are there reasons to keep overrides like this only on the top-level?

[berberman]

Thanks for noting that, the upcoming version requires generateOptparseApplicativeCompletion, and I'll add this new one and move them to configuration-common.nix at once.

[cdepillabout]

@maralorn Ah, good point. I'll make sure to check for that in the future.