refactor(s3stream): automate logIdent injection via LogContext

[misi0202]

Using com.Automq.Stream.Utils.LogContext for com.Automq.Stream.S3.S3Stream logIdent automatic injection in prefix

Summary of testing strategy (including rationale)
Test the log output format in S3Stream

Committer Checklist (excluded from commit message)

• [✅] Verify design and implementation
• [✅] Verify test coverage and CI build status

[CLAassistant]

All committers have signed the CLA.

[Chillax-0v0]

Hi @misi0202,

I noticed your workflow for requesting changes on PRs and wanted to share a GitHub best practice that might help improve collaboration. When a pull request needs revisions, converting it to a draft (rather than closing it) is generally recommended.

This approach preserves the conversation history and context while clearly indicating the work-in-progress status to collaborators. It also avoids generating multiple closed/reopened event notifications, which can sometimes cause confusion in tracking changes.

The draft feature was introduced specifically for this purpose - you can easily convert PRs using the right sidebar dropdown. When ready, it can be marked "Ready for review" again without losing any context.

Just sharing this as a friendly suggestion – feel free to ignore if you have a specific reason for your current approach!

[misi0202]

Hi @misi0202,

I noticed your workflow for requesting changes on PRs and wanted to share a GitHub best practice that might help improve collaboration. When a pull request needs revisions, converting it to a draft (rather than closing it) is generally recommended.

This approach preserves the conversation history and context while clearly indicating the work-in-progress status to collaborators. It also avoids generating multiple closed/reopened event notifications, which can sometimes cause confusion in tracking changes.

The draft feature was introduced specifically for this purpose - you can easily convert PRs using the right sidebar dropdown. When ready, it can be marked "Ready for review" again without losing any context.

Just sharing this as a friendly suggestion – feel free to ignore if you have a specific reason for your current approach!

Thanks for your suggestion,I have changed this PR to draft and I did modify two files by mistake.

[misi0202]

@Chillax-0v0 After I committed the changes to change the mistakes, bulid S3stream in E2E-TEST for AutoMQ S3Stream encountered the following error message. Shown as automq/stream/s3 / operator/TrafficVolumeLimiter.java appear problem, whether this modified code with me, thank you for your guidance and reply.

[Chillax-0v0]

@Chillax-0v0 After I committed the changes to change the mistakes, bulid S3stream in E2E-TEST for AutoMQ S3Stream encountered the following error message. Shown as automq/stream/s3 / operator/TrafficVolumeLimiter.java appear problem, whether this modified code with me, thank you for your guidance and reply.

Apologies for the confusion. The S3Stream E2E Test has been recently broken, and this error is unrelated to your changes in this PR.
You can safely ignore this error message - the specific Action for S3Stream E2E Test won't be triggered before merging anyway. Thank you for your contribution and for double-checking!