perl536Packages: cross fixes

[apfelkuchen6]

Description of changes

This fixes the cross compilation of several perl packages that are in the closure of biber.

Most of these fixes are simply adding buildPackages.perl to nativeBuildInputs. This doesn't change anything for native builds since these pull in perl anyway. Cross builds use a minimal perl copy perl.mini (this does not exist for native), which suffices for bootstrapping perl and running simple build scripts, but not for the builds scripts of the derivations changed here: They mostly fail with error messages like

perl says : Can't load module B, dynamic loading not available in this perl
  (You may need to build a new perl executable which either supports
  dynamic loading or has the B module statically linked into it.)
 at (eval 11) line 1.

I can split this into multiple PRs if desirable, but most of the builds cannot be tested indepentently because of many inter-dependencies.

Things done

• Built on platform(s)
  • x86_64-linux (native and for aarch64).
  • 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.

[ck3d]

We should provide a comment to this hack and the assignment (which is an implicit override of perl.mini) should only be done for cross-compilation (to document the intention).

[apfelkuchen6]

My thought process behind not guarding was "a full perl is also required for native builds, so this is just more explicit". On the other hand, guarding this with /nix/store/av8clvjy4d91ybmsc92lgaxnvlif4g6l-perl5.36.0-Alien-Build-2.37-i686-unknown-linux-gnu.drv also has the additional benefit that it doesn't change the evaluation for native builds, (hopefully) cutting down the number of rebuilds significantly. Will update.

Adding a simple comment like "when cross-compiling, buildPerlPackage only appends perl.mini to nativeBuildInputs, but this build needs a full perl" to each of these lines should be enough, right?
edit: the wording from your PR #222427 ("Override default intepreter perl.mini") is better

[apfelkuchen6]

Marked as draft for now, see #222427