Skip Azure Blob folder-marker keys in AzureBlobStorageToS3Operator

[yuseok89]

AzureBlobStorageToS3Operator copies every name WasbHook.get_blobs_list_recursive() returns, including the trailing-/ folder markers a container listing contains. They land in S3 as spurious empty keys and in the XCom output.

This applies the same overlap-aware rule introduced for GCSToS3Operator in #72497. The filtering logic is now shared by both operators through an Amazon transfer utility: a trailing-/ key is dropped only when it is also a strict prefix of another key in the same listing, so a real object like lonely/ is kept. The filter runs right after the listing, so the upload, the replace=False comparison, and the XCom output all see the same list.

Skipped keys are logged, and the returned list is now sorted and de-duplicated.

Before / After

Listing: src/ (a marker), src/file.txt, and lonely/ (a real object whose name ends in /).

	S3 keys	XCom
Before	src/, src/file.txt, lonely/	all three
After	src/file.txt, lonely/	those two

Verified end to end against a real Azure storage account and a real S3 bucket, with the markers created through the Blob API.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  • Opus 5

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[o-nikolas]

Left a couple comments, otherwise looks good to me