curl: add hyper support

[getchoo]

Closes #357409

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.

[JohnRTitor]

This should target staging.

[JohnRTitor]

since it's actually false, we are not shipping curl with hyper, unlike what the post wants.

I would let the issue stay open and change the issue title to "curl: move to the hyper backend".
I think it's great to add the support by default, once it is stable, that is.

[JohnRTitor]

Upstream does not commit their lockfiles?

I think a better approach would be to ask upstream to commit their lockfile, mentioning our reproducibility requirements which needs the lockfile to compare the hash with.

[pluiedev]

Hyper is usually used as a library, and Cargo's commit guidelines generally advise against including a Cargo.lock for libraries

Apparently that's a historical practice: https://doc.rust-lang.org/cargo/faq.html#why-have-cargolock-in-version-control leaves the choice open while stating that Cargo.lock doesn't affect library consumers. I guess it's okay to ask them to add a Cargo.lock then

[getchoo]

Opened hyperium/hyper#3788

[niklaskorz]

Curl has officially removed hyper support: https://daniel.haxx.se/blog/2024/12/21/dropping-hyper/

The hyper backend code has been removed in git as of December 21. There will be no traces left of it in the curl 8.12.0 release coming in February 2025.