Remove guess on region

[guilhem]

This prevent s3cmd to fail with other s3 implementations

Fix #859

[benhowell]

👍
Agree. I patched s3cmd myself to make it work with DigitalOcean spaces and came here to make a pull request. But here it is already ;-)

[fviard]

@guilhem @benhowell Sorry, I didn't understood this issue and the proposed PR, but I hadn't time to look deeper into this issue before.

Based on @benhowell, I opened a DO space to try s3cmd with it to try to reproduce any issue, but I can't. So I supposed that it was patched on their side.

Is it possible for one of you to describe me in details that was the issue/root cause, and why this PR would have fixed that? (even if maybe it is fixed with DO).
I look at #859 but I don't understand how the "location" value as any relation with naming a bucket "eu" or "us"? My best guess would be that you use to have a dynamic "location" field in your host_bucket config where "regions" are not supported by DO.

[rampageservices]

I used DO for the first time with this tool.
The tutorial here says to ignore the region as it is not relevant: https://docs.digitalocean.com/products/spaces/reference/s3cmd/#enter-access-keys
It would be great if for DO this simply did not show up as it was confusing even for a first-time extremely technical user like myself.