Dont use DNS style addressing for GetBucketLocation

This fixes an issue when you try to get bucket location
for a bucket in eu-central-1.  You now do not need a region
specified.

For example, you previously needed:

```
$ aws s3api get-bucket-location --bucket jamesls-eu-central-1 --region eu-central-1
{
    "LocationConstraint": "eu-central-1"
}
```

which defeated the purpose of get-bucket-location.  Now the region doesn't matter:

```
$ aws s3api get-bucket-location --bucket jamesls-eu-central-1 --region us-east-1
{
    "LocationConstraint": "eu-central-1"
}
$ aws s3api get-bucket-location --bucket jamesls-eu-central-1 --region us-west-2
{
    "LocationConstraint": "eu-central-1"
}
$ aws s3api get-bucket-location --bucket jamesls-eu-central-1 --region ap-northeast-1
{
    "LocationConstraint": "eu-central-1"
}
```


cc @kyleknap @danielgtaylor 
Yeah good point.  I'll update what all the test fixture setup/teardown to use clients.  I think we still need the service/operation in the actual tests themselves (in addition to the client interfaces) until we can actually deprecate the service/operation objects.