enhancement(aws_s3 sink): Emit log when putting an object to s3-compatible storage

[5Dev24]

Summary

This creates a log event went writing to an s3-compatible storage. This is intended to allow for the log to be captured with the internal_logs source and use the bucket and key to send off to another sink.

How did you test this PR?

Setting VECTOR_LOG to vector::sinks::s3_common::service::put_object=trace,info.

Change Type

• Bug fix
• New feature
• Non-functional (chore, refactoring, docs)
• Performance

Is this a breaking change?

• Yes
• No

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
• No. A maintainer will apply the no-changelog label to this PR.

References

Related: #22994
Related: #23234 (4 of 4)

Notes

• Please read our Vector contributor resources.
• Do not hesitate to use @vectordotdev/vector to reach out to us regarding this PR.
• Some CI checks run only after we manually approve them.
  • We recommend adding a pre-push hook, please see this template.
  • Alternatively, we recommend running the following locally before pushing to the remote branch:
    • cargo fmt --all
    • cargo clippy --workspace --all-targets -- -D warnings
    • cargo nextest run --workspace (alternatively, you can run cargo test --all)
• After a review is requested, please avoid force pushes to help us review incrementally.
  • Feel free to push as many commits as you want. They will be squashed into one before merging.
  • For example, you can run git merge origin master and git push.
• If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
  run cargo vdev build licenses to regenerate the license inventory and commit the changes (if any). More details here.

[maycmlee]

Couple of small suggestions

[5Dev24]

Can no-changelog be added to this PR?