S3-credentials

- Fixed documentation bug. [s3-credentials.readthedocs.io](https://s3-credentials.readthedocs.io/) should now show the most recent stable release documentation.

- New command: `s3-credentials debug-bucket bucket-name`. [86](https://github.com/simonw/s3-credentials/issues/86)
- Fixed bug where calling `s3-credentials create bucket-name --create-bucket --public` did not make the contents of the bucket available to the public. [88](https://github.com/simonw/s3-credentials/issues/88)
- `s3-credentials list-bucket bucket-name --urls` option. [89](https://github.com/simonw/s3-credentials/issues/89)

- New `s3-credentials delete-objects` command ([docs](https://s3-credentials.readthedocs.io/en/stable/other-commands.html#delete-objects)) for deleting one or more keys from the specified bucket. [83](https://github.com/simonw/s3-credentials/issues/83)

- `s3-credentials put-objects` command ([docs](https://s3-credentials.readthedocs.io/en/stable/other-commands.html#put-objects)) for uploading more than one file or directory to an S3 bucket at a time. [68](https://github.com/simonw/s3-credentials/issues/68)
- `s3-credentials get-objects` command ([docs](https://s3-credentials.readthedocs.io/en/stable/other-commands.html#get-objects)) for downloading multiple files from an S3 bucket. [78](https://github.com/simonw/s3-credentials/issues/78)

- Documentation now lives on a dedicated documentation website: https://s3-credentials.readthedocs.io/ [#71](https://github.com/simonw/s3-credentials/issues/71)
- `s3-credentials create ... --website --create-bucket` now creates an S3 bucket that is configured to act as a website, with `index.html` an the index page and `error.html` as the page used for any errors. [21](https://github.com/simonw/s3-credentials/issues/21)
- `s3-credentials list-buckets --details` now returns the bucket region and the URL to the website, if it is configured to act as a website. [77](https://github.com/simonw/s3-credentials/issues/77)
- Fixed a bug where `list-bucket` would return an error if the bucket (or specified `--prefix`) was empty. [76](https://github.com/simonw/s3-credentials/issues/76)

- Using the `--policy` or `--statement` options now implies `--user-permissions-boundary=none`. Previously it was easy to use these options to accidentally create credentials that did not work as expected since they would have a default permissions boundary that locked them down to only being able to access S3. [74](https://github.com/simonw/s3-credentials/issues/74)
- The `s3-credentials.AmazonS3FullAccess` role created by this tool in order to issue temporary credentials previously used the default `MaxSessionDuration` value of 3600, preventing it from creating credentials that could last more than an hour. This has been increased to 12 hours. See [this issue comment](https://github.com/simonw/s3-credentials/issues/75#issuecomment-1201643771) for instructions on fixing your existing role if this bug is affecting your account. [75](https://github.com/simonw/s3-credentials/issues/75)