fix S3 PUT operations returning HTTP Body by default

[bentsku]

Motivation

As reported in #9032, some S3 operations (the one using the PUT http method) would return an empty XML body when the S3 docs specifies that the body should be empty. After looking at the specs, only CopyObject and CopyObjectPart would return a body. Luckily, those operations implement a field specifying that they return a body, the payload one.

Changes

Removed the pre-signed handler deleting the response body, since this behaviour should have been for every PUT request except some, and it was actually fixing a symptom instead of the cause.

Implemented a check in the serializer for not serializing a body if the conditions were not set (if it's a PUT request without the payload field).

Added 2 cases in a test checking the raw returned body without boto parsing, one for a known PUT operation which should return a body (CopyObject) and one for UploadPart, which should not return a body.

[coveralls]

coverage: 80.45% (-0.001%) from 80.451% when pulling ada3209 on fix-s3-put-method-return-body into 5217b87 on master.

[github-actions]

LocalStack Community integration with Pro

       2 files         2 suites   1h 24m 30s ⏱️
2 151 tests 1 677 ✔️ 474 💤 0 ❌
2 152 runs  1 677 ✔️ 475 💤 0 ❌

Results for commit ada3209.

[alexrashed]

Nice! Really great to see how much indirections can be removed with just handling that one condition on a global level in the serializer! 🚀