libjpeg_turbo: 2.1.5.1 -> 3.0.0

[risicle]

Description of changes

I would mark this with a Security label due to https://nvd.nist.gov/vuln/detail/CVE-2023-2804, but I'm fairly certain that doesn't apply to us, because it's specifically in the 12-bit code and we don't build with 12-bit enabled.

Also successfully built pkgsStatic, pkgsMusl & pkgsCross.aarch64-multiplatform variants.

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.

[vcunat]

There are API-breaking changes, so I don't expect it will be smooth so soon after releasing upstream.

[risicle]

Possibly. However, it looks like the API changes are in the turbojpeg API, and I suspect the vast vast majority of packages will be using the libjpeg API.

[risicle]

Looks like you're right and we have our first candidate.

@ofborg build graphicsmagick

[risicle]

This seems to solve it

@ofborg build graphicsmagick

[alyssais]

Done in #285136.