GH-50148: [C++] Add Content-Encoding support to S3 filesystem metadata

[alytantawyy]

Rationale for this change

The S3 filesystem metadata handling supported headers such as Content-Type,
Content-Language, Cache-Control, and Expires, but omitted
Content-Encoding.

As a result, Content-Encoding was not propagated when writing S3 object
metadata, and it was also not returned when reading metadata back.

What changes are included in this PR?

• add Content-Encoding to S3 object metadata extraction
• add Content-Encoding to the S3 metadata setter whitelist
• reuse the existing string metadata setter for Content-Encoding
• extend the S3 metadata round-trip test to cover explicit and default
  Content-Encoding metadata

Are these changes tested?

Yes.

./cpp/build-s3-system/debug/arrow-s3fs-test --gtest_filter=TestS3FS.OpenOutputStreamMetadata

• GitHub Issue: [C++] content-encoding field missing from s3 fs. #50148

[pitrou]

@raulcd @kou I have no idea why the CUDA Python jobs have run here, as I only see non-CUDA C++ changes?

[raulcd]

I have no idea why the CUDA Python jobs have run here, as I only see non-CUDA C++ changes?

This is weird, all extra jobs are running not only CUDA but R Extra, Packaging Extra, C++ Extra and it does not seem like any of the required labels were ever present.

[raulcd]

ok, the PR seems to be quite outdated with respect to main so the git diff when checking labels seems to show lots of files changed and forces the jobs to run as some of those files trigger the them, see: https://github.com/apache/arrow/actions/runs/27442216149/job/83430959300?pr=50167#step:3:39

[pitrou]

@alytantawyy Can you please first rebase or merge from git main as it seems this PR is based on a quite outdated snapshot of the source tree?

[alytantawyy]

@pitrou @raulcd @kou Rebased onto the latest main. The targeted S3 metadata test passes locally.

[kou]

Could you fix the lint failure?

[kou]

Can we use StringSetter(&ObjectRequest::SetContentEncoding)?

Suggested change

	{"Content-Encoding", ContentEncodingSetter()},
	{"Content-Encoding", StringSetter(&ObjectRequest::SetContentEncoding)},

[alytantawyy]

Updated to use StringSetter(&ObjectRequest::SetContentEncoding) and fixed the clang-format failure. The targeted S3 metadata test passes locally. @kou @raulcd

[alytantawyy]

@kou @raulcd following up

[kou]

+1