I had to hunt around for this, and the first place
I looked was the Makefile (where I would expect
code generation to occur).

There are two names the bucket name can get
encoded into the request URL, either as a
subdomain prepended to the host, or as the first
member in the path. Handle both of these, as we
don't have control over which will be used.

Even if explicitly set in the config to use the
hosted bucket style, it might only be able to do
the path style.

https://github.com/aws/aws-sdk-go/blob/main/aws/config.go#L118-L127

also, add make target that will update the file if
a new module is created.

seems the tests are failing to build on older
versions of go

This reverts commit 6b84892.

This reverts commit 052125a.

As mentioned in the comment, after 3 attempts I
wasn't able to find an S3 request that used the
virtual bucket style pathing (which is supposed to
be the default). I opted to test the function for
now, even though it's private.

If the bucket name is all caps, it forces the path
style URL structure; if the bucket name is
lowercase, it will default to virtual bucket
style. Test that both cases are handled.

this looks a bit like overkill now, but when we
add additional aws services it will be worth it.

This is most likely less expensive than reading
out the body, unmarshaling it into a struct (the
process itself already using reflection), and then
attaching a new copy of the body back to the
request.