build(deps): update acme requirement from ~=2.5.0 to ~=2.6.0

[dependabot]

Updates the requirements on acme to permit the latest version.

Release notes

Sourced from acme's releases.

Certbot 2.6.0

Added

• --dns-google-project optionally allows for specifying the project that the DNS zone(s) reside in, which allows for Certbot usage in scenarios where the auth credentials reside in a different project to the zone(s) that are being managed.
• There is now a new Other annotated challenge object to allow plugins to support entirely novel challenges.

Changed

• Optionally sign the SOA query for dns-rfc2136, to help resolve problems with split-view DNS setups and hidden primary setups.
  • Certbot versions prior to v1.32.0 did not sign queries with the specified TSIG key resulting in difficulty with split-horizon implementations.
  • Certbot v1.32.0 through v2.5.0 signed queries by default, potentially causing incompatibility with hidden primary setups with allow-update-forwarding enabled if the secondary did not also have the TSIG key within its config.
  • Certbot v2.6.0 and later no longer signs queries by default, but allows the user to optionally sign these queries by explicit configuration using the dns_rfc2136_sign_query option in the credentials .ini file.
• Lineage name validity is performed for new lineages. --cert-name may no longer contain filepath separators (i.e. / or \, depending on the platform).
• certbot-dns-google now loads credentials using the standard Application Default Credentials strategy, rather than explicitly requiring the Google Compute metadata server to be present if a service account is not provided using --dns-google-credentials.
• --dns-google-credentials now supports additional types of file-based credential, such as External Account Credentials created by Workload Identity Federation. All file-based credentials implemented by the Google Auth library are supported.

Fixed

• certbot-dns-google no longer requires deprecated oauth2client library.
• Certbot will no longer try to invoke plugins which do not subclass from the proper certbot.interfaces.{Installer,Authenticator} interface (e.g. certbot -i standalone will now be ignored). See GH-9664.

More details about these changes can be found on our GitHub repo.

Commits

• 013621d Release 2.6.0
• e0e2bfe Update changelog for 2.6.0 release
• d2e2a92 update farm tests (#9687)
• 6e52695 dns-rfc2136: add test coverage for PR #9672 (#9684)
• 5b5a2ef squelch warnings (#9689)
• 8a0b0f6 Support unknown ACME challenge types (#9680)
• 10fba2e docs: clarify --dry-run documentation (#9683)
• 67f14f1 ignore invalid plugin selection choices (#9665)
• f378ec4 Optionally sign initial SOA query (#9672)
• b0d0a83 google: use Application Default Credentials where available (#9670)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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)