Bug 2299642

Description of problem:
As described in upstream https://tracker.ceph.com/issues/64308 having CORS set on the bucket and adding CORS headers to presigned PUT requests fails with 403 due to the header `x-amz-acl` not being considered when signing.


Version-Release number of selected component (if applicable):
7.1 (upstream  17.2.7+ based)

How reproducible:
everytime 

Steps to Reproduce:
1. set bucket acl
```
aws s3api put-bucket-acl --bucket=<user> --cors-configuration='{"CORSRules":[{"AllowedHeaders":["Authorization"],"AllowedMethods":["GET","PUT"],"AllowedOrigins":["example.com"],"ExposeHeaders":["ETag","x-amz-request-id"],"MaxAgeSeconds":3000}]}'
```

2. create presigned put uri
```
presigned = s3.generate_presigned_url(
    ClientMethod="put_object",
    HttpMethod='PUT',
    Params={
        "Bucket": "bucket",
        "Key": "test",
        "ACL": "private",
    },
)
```

3. use curl with CORS headers to post content

```
curl -X PUT 'https://s3.example.com/user1/plain-test?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=user1%2F20240724%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20240724T070246Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host%3Bx-amz-acl&X-Amz-Signature=6d2f5ca1845c5fb71890588f82480b320281bc6bb2e2ab93d12fdfc1d25a728f' -d 'testing' -H 'origin: example.com' -H 'access-control-request-method: PUT' -d 'testing curl'
```


Actual results:
```
HTTP code: 403
<?xml version="1.0" encoding="UTF-8"?><Error><Code>AccessDenied</Code><Message></Message><RequestId>tx000000ad5acbcf928f265-0066a0a716-1f39666-us-east-1</RequestId><HostId>1f39666-us-east-1-us-east-1</HostId></Error>
```


Expected results:
```
HTTP code: 200
```

Additional info:
There are two mitigations right now in place. Both are not sufficient as:

Workaround1 (drop ACL from presigned PUT):
```
presigned = s3.generate_presigned_url(
    ClientMethod="put_object",
    HttpMethod='PUT',
    Params={
        "Bucket": "bucket",
        "Key": "test",
    },
)
``` 

does not result in 403 but implies access to the source code of the applications (not always possible)

Workaround2 (drop CORS acl from Bucket):
implies unexpected access through third party requests which is the reason to have CORS set.
^^^ 

seem's to be not working out too as the CORS headers would need to be removed prior reaching the RGW endpoint