feat(services/s3): add S3 tagging write support

[jackye1995]

Summary

This PR implements comprehensive tagging support for S3 write operations with the ability to disable it when needed, following the pattern used in the Arrow object_store implementation.

Changes

• ✅ Add disable_tagging configuration option to S3Config and S3Builder
• ✅ Add tags field to WriteOptions and OpWrite for specifying object tags
• ✅ Implement tag header generation in S3Core::insert_metadata_headers with proper URL encoding
• ✅ Add write_with_tags capability to indicate tagging support
• ✅ Include comprehensive unit tests for tagging functionality

Motivation

Some S3-compatible backends don't support object tagging, or users may want to reduce request overhead when tags aren't needed. This feature provides:

• Full tagging support when enabled (default behavior)
• Option to disable tagging for compatibility with backends that don't support it
• Performance optimization by skipping tag processing when not needed
• Follows established patterns from Azure object_store implementation

Usage

// Enable tagging (default)
let builder = S3Builder::new()
    .bucket("my-bucket");

// Disable tagging for compatibility
let builder = S3Builder::new()
    .bucket("my-bucket")
    .disable_tagging();

// Write with tags
let mut tags = HashMap::new();
tags.insert("Environment".to_string(), "Production".to_string());
tags.insert("Team".to_string(), "Engineering".to_string());

op.write("path/to/file")
    .tags(tags)
    .await?;

Implementation Details

• Tags are sent via the x-amz-tagging header in URL-encoded format
• Tag keys and values are properly encoded to handle special characters
• When disable_tagging is true, no tag processing occurs (zero overhead)
• The write_with_tags capability reflects whether tagging is enabled

Test plan

• Unit test verifies tags are included in headers when tagging is enabled
• Unit test verifies tags are excluded when tagging is disabled
• Proper tag formatting and URL encoding verified
• All existing tests pass
• cargo check --features services-s3 passes
• cargo test --features services-s3 passes

🤖 Generated with Claude Code

[tisonkun]

Could you provide the source of this logic? I suppose that S3's docs or other materials define it.

[Xuanwo]

Hi, @jackye1995 Thank you for working on this!

Adding a new feature such as writing with tags requires an RFC that considers all possible services. We need to conduct research on at least three major object storage vendors, such as S3, GCS, and Azure.

[jackye1995]

Sounds good let me do that first following the process, will revert this as a draft for now