[staging] python3Packages.setuptools: 57.2.0 -> 60.5.0

[jonringer]

Motivation for this change

cherry-picked from #154969 (cherry picked from commit 410658a)

Since setuptools removed use_2to3 internal option, many packages were broken.

This doesn't have an "easy" solution, as it usually means that the upstream still has a
significant amount of python2 code, and without vendoring 2to3, there's not easy way for
the package to be installed with python3

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

[ghost]

LGTM!

[FRidh]

Why do you want to cherry-pick this to staging? So to keep track of for another time?

[jonringer]

Why do you want to cherry-pick this to staging? So to keep track of for another time?

it's a mass rebuild. And my server can handle the build load. I can rebase onto master for others

[mweinelt]

Superseded by #160067