Users have reported that some S3 backend implementations potentially implement the list v2 endpoint in a way that is not compatible with the upstream implementation of the velero aws plugin.

We'd like to provide a solution that will gracefully degrade the client to our known, good v1 call should the server not implement the expected v2 endpoint.

We suspect Swift to be a problem backend that produces indeterminate behavior.