tests: adapt s3 acl tests to new default behavior

[evgeniiz321]

closes #885

[evgeniiz321]

@roman-khimov shouldn't it be 2 different actions to enable ACLs for objects and buckets? Right now this command:

s3_bucket.put_bucket_policy(
                    self.s3_client,
                    bucket,
                    {
                        "Statement": [
                            {
                                "Sid": "BucketEnableACL",
                                "Effect": "Allow",
                                "Action": ["s3:PutObject"],
                                "Resource": ["*"],
                            }
                        ],
                    },
                )

Enables ACLs both for objects and buckets, another thing - only this Action is accepted - "Action": ["s3:PutObject"],, all other cause 500 from s3 gw.

[roman-khimov]

I think it's better to be verified against Amazon. But I've also found nspcc-dev/neofs-s3-gw#1023 and nspcc-dev/neofs-s3-gw#1022.

[evgeniiz321]

@smallhive why are we requiring this: header x-amz-acl:bucket-owner-full-control must be set after we enable ACL? With this restriction the only ACL that we can set is bucket-owner-full-control, but we should be able to set whatever we want, if we decided to enable ACL.

[smallhive]

header x-amz-acl:bucket-owner-full-control must be set

It should be valid, in the preferred mode only. In object writer, it should work fine with any ACLs.
I did this according to docs, but it works without the bucket policy (this policy requires bucket-owner-full-control ACL), described in the docs

[evgeniiz321]

@smallhive @roman-khimov this is different from the amazon behavior. With BucketOwnerPreferred, any object ACLs can be set, if there are no other policies. But if a bucket owner wants, there is a possibility to add a policy to make object writers to forcefully specify bucket-owner-full-control. This is what docs is about. This behavior shouldn't be enforced by default, but should be enabled via policies. If we want to behave the same as the amazon s3 implementation.

[roman-khimov]

Move it to additional issue, please. This can be fixed, so it should be fixed.