feat(perlPackages): add CPAN packages required by LedgerSMB

[freelock]

Added a bunch of CPAN modules that the LedgerSMB program needs, as a first step to creating a package for it. I also updated several existing CPAN modules that could no longer be loaded because the CPAN mirrors were returning 404.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• 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/)
• 25.05 Release Notes (or backporting 24.11 and 25.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.

---

Add a 👍 reaction to pull requests you find important.

[SigmaSquadron]

To recap what we discussed on matrix:

1. Please review our Commit Conventions and reword/split your commits appropriately; their titles must follow very specific patterns as defined in our documentation. Don't forget to squash your intermediate/fixup commits.
   • This means that if you're adding 160 packages, we want to see 160 commits and no fixup/style/formatting commits after those.
2. You're accidentally changing packages that cause mass rebuilds. Please remove your changes to TermTable and any other dependencies that aren't related to your package additions.
   • Forgive our knee-jerk reaction to this, but Nixpkgs is part of the critical dependency path for several downstreams, and large, unexplained rebuilds are often the sign that something nefarious is afoot.
   • You can add these mass-rebuild changes to a separate PR targeting the staging branch.
3. Please add your maintainer information to maintain these packages. More information is available in the Maintainers' README.
4. It might be best to remove these packages from perl-packages.nix and move them to development/perl-modules, or ideally by-name.