Remove s3 bucket creation

[dgzlopes]

What this PR does:
Removes the code that creates the S3 bucket.

Which issue(s) this PR fixes:
Fixes #401

Checklist

• Tests updated
• Documentation added
• CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

[mdisibio]

This is great thank you.

A couple thoughts:

• Do you know if the min.io example needs to be updated to create the bucket initially, or is ok?
• I think we can remove the s3 config Region value entirely now. Min.IO can infer the region from the endpoint url.

[dgzlopes]

Thank you for taking the time to review :)

• I'm not fully sure, I'll research it tomorrow - I've to leave.
• Nice! Removed.

[dgzlopes]

@mdisibio In theory, the Minio example should work b/c here:

# from docker-compose.s3.minio.yaml line:24
mkdir -p /data/tempo && /usr/bin/minio server /data

When we create the new folder, we're creating a new bucket too.

[annanay25]

LGTM. Thanks @dgzlopes!

[faceair]

Hi guys, the region field is useful.

There are many s3-compatible object stores that rely on this field when calculating signatures, and their endpoint is completely different from s3. For example, Baidu's object store https://cloud.baidu.com/doc/BOS/s/xjwvyq9l4