[23.11] liquidctl: fix test for pillow ≥ 10.2.0

[evils]

issue described upstream in
liquidctl/liquidctl#661

Description of changes

added patch linked in upstream issue
(liquidctl/liquidctl@c50afa4)

Things done

manual backport of #288085
verified this does not break liquidctl before #284251 gets to 23.11

• 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
  nixpkgs-review failed to automatically merge ¯\_(ツ)_/¯
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.05 Release Notes (or backporting 23.05 and 23.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.

---

Add a 👍 reaction to pull requests you find important.

[evils]

@Kranzes why did you close this?
this is a manual backport for the soon to be affected 23.11 branch
(manual as the main PR's changes cannot be applied to the 23.11 branch directly)

[Kranzes]

Oh I thought It was a duplicate of the other branch. I guess that's why you should follow CONTRIBUTING.md properly and name your PR accordingly. If you ever want to backport a PR just add the backport label to it and a GitHub Action will handle creating the backport PR.

[evils]

i knew about the github action, that's not applicable here as the commits in the other PR don't apply cleanly to the 23.11 branch

i did read the relevant section in CONTRIBUTING.md, but apparently stopped reading when it clarified what branch to target after saying i should use the regular PR rules to create the backport (which i assumed included the unabridged rules about titling)

[evils]

please read CONTRIBUTING.md before changing my title

[Kranzes]

please read CONTRIBUTING.md before changing my title

You're right, my bad. There seems to be some inconsistencies between the Github Action and the CONTRIBUTING.md.