⬆ Bump setuptools from 67.7.2 to 80.9.0

[dependabot]

Bumps setuptools from 67.7.2 to 80.9.0.

Changelog

Sourced from setuptools's changelog.

v80.9.0

Features

• Set a deadline for the removal of pkg_resources later this year (December). (#3085)
• Removed reliance on pkg_resources in test_wheel. (#3085)

v80.8.0

Features

• Replaced more references to pkg_resources with importlib equivalents in wheel odule. (#3085)
• Restore explicit LICENSE file. (#5001)
• Removed no longer used build dependency on coherent.licensed. (#5003)

v80.7.1

Bugfixes

• Only attempt to fetch eggs for unsatisfied requirements. (#4998)
• In installer, when discovering egg dists, let metadata discovery search each egg. (#4998)

v80.7.0

Features

• Removed usage of pkg_resources from installer. Set an official deadline on the installer deprecation to 2025-10-31. (#4997)

Misc

• #4996

v80.6.0

Features

... (truncated)

Commits

• 9c4d383 Bump version: 80.8.0 → 80.9.0
• 05cb3c8 Merge pull request #5014 from pypa/debt/pkg_resources-deadline
• 3b0bf5b Adjust ignore
• 9c28cdf Set a deadline for the removal of pkg_resources later this year (December).
• a3bfef9 Merge pull request #5013 from DimitriPapadopoulos/ISC
• 64bf9d0 Enforce ruff/flake8-implicit-str-concat rules (ISC)
• 3250c25 Fix broken link in docs (#4947)
• 5ccf50e Merge pull request #5006 from pypa/feature/remove-more-pkg_resources
• 134e587 Suppress nitpicky typecheck in pyright.
• 0bf2663 Add news fragment.
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mpryc for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a dora-metrics member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.