new test case suggestion: bucket creation with ACL

Hi,

one common action for many s3 clients, such as cyberduck, is to set ACLs for a bucket at the same time as it is being created. This would be a valuable test case, as the having the X-Amz-Acl header set could be treated differently when creating a bucket - it caught me out when working on swift, at least :)

I'm not sure what boto sends, but here's an example request from cuberduck:

PUT /lol/ HTTP/1.1
Date: Tue, 16 Oct 2012 22:56:57 GMT
x-amz-acl: public-read
Content-Type: application/octet-stream
Authorization: AWS admin:admin:qibESADS8jtU8aZTJa2K0KJqo1g=
Content-Length: 0
Host: 192.168.1.20:443
Connection: Keep-Alive
User-Agent: Cyberduck/4.2.1 (Mac OS X/10.8.2) (i386)

No file or existing test is named. Start by locating the bucket-creation tests and checking how boto sends the x-amz-acl header, using the Cyberduck request as a reference. Done means coverage exists for creating a bucket with an ACL such as public-read and the expected S3 behavior is verified.

Written by the indexing model from the issue text.