cacert: 3.77 -> 3.80

[ajs124]

Description of changes

Contains #178809, but targeted against staging, because cacert

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/)
• 22.11 Release Notes (or backporting 22.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
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[github-actions]

Backport failed for staging-21.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally.

git fetch origin staging-21.11
git worktree add -d .worktree/backport-178862-to-staging-21.11 origin/staging-21.11
cd .worktree/backport-178862-to-staging-21.11
git checkout -b backport-178862-to-staging-21.11
ancref=$(git merge-base add6a3b7dc1d693654e2973456a0d4992cd38911 04be37dead641c3d08cc179428e106e01352c907)
git cherry-pick -x $ancref..04be37dead641c3d08cc179428e106e01352c907

[github-actions]

Successfully created backport PR #179343 for staging-22.05.

[vcunat]

Uh, well now we have two different commits doing the same nss update (on staging, later master), but it's certainly not a big deal.

[ajs124]

Uh, well now we have two different commits doing the same nss update (on staging, later master), but it's certainly not a big deal.

Would not updating in this PR nss_latest have been the preferred option? If so, I'll try and remember to do that, next time.

[vcunat]

Maybe, or we could've used the squash-merge button, as at merge time it was already included in staging.