Bump python-swiftclient from 1.9.0 to 2.0

[dependabot]

Bumps python-swiftclient from 1.9.0 to 2.0.

Changelog

Sourced from python-swiftclient's changelog.

swift (2.32.0, OpenStack Bobcat)

* Python 3 fixes:


Python 3 object servers can now read unencrypted non-ASCII metadata
that was written under Python 2.


Ssync no longer corrupts unencrypted non-ASCII metadata during
transfers.


Fixed an encoding issue when writing non-ASCII object names to sharded
containers and shard range caching is not enabled.


Fixed an encoding issue when handling non-ASCII account names.


Fixed a generator already executing error on client disconnect.


Suppressed RemoteDisconnected tracebacks.


Metrics improvements:


Metrics are now emitted for a variety of S3 error responses, in the
form s3api.<status_int>.<error_class>[.<reason>]


Fixed an issue that prevented proxy servers from emitting metrics and
logs for backend requests made when getting account or container info.


Account and container info metrics now include the response status code
when backend requests are made.


Added timing metrics to the container sharder for various operations.




Python 3.11 is now supported.


Added the ability for reseller admins to set per-policy account quotas by
posting metadata of the form X-Account-Quota-Bytes-Policy-<policy name>.


Added a keepalive_timeout option to the proxy server to limit how long
to wait for a client to initiate a request, separate from the general
client_timeout option. Note that this requires eventlet 0.33.4
(currently unreleased) or later.


Added a keep_cache_slo_manifest option to the object server to better
control whether SLO manifests are dropped from the page cache.


WSGI servers now accept a --test-config option that may be used to
validate configuration changes before reloading/restarting the server.


The structure of cached shard ranges has changed, improving performance
when listing or writing to sharded containers. Note that immediately

... (truncated)

Commits

• bfa9139 Fix potential missing key error in container_info
• 7dbf832 Fix pop_queue for move object twice
• fb5a0f2 Fix KeyError on Storage Policy Container Sync
• 1feaf6e release notes for Swift 2.0
• 53d4d21 Merge storage policies feature commit chain into master
• e52e8bc Add Storage Policy Documentation
• c1dc2fa Add two vector timestamps
• 8d20e0e Fix object-expirer for missing objects
• 2e1ea82 Add Storage Policy support to the Account Reaper
• 8326dc9 Add Storage Policy Support to Recon Middleware
• 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 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.