feat(services/s3): add conditional delete with if-match

[YuangGao]

Which issue does this PR close?

Closes #7090.

Rationale for this change

AWS S3 supports If-Match on DeleteObject since 2024 (docs). Expose it through OpenDAL so callers can do CAS-style conditional deletes

What changes are included in this PR?

Core:

• Add Capability::delete_with_if_match.
• Add if_match: Option<String> to OpDelete, DeleteOptions, and a FutureDelete::if_match builder.
• Add the matching check in correctness_check.rs

S3:

• Set delete_with_if_match: true on the S3 capability.
• s3_delete_object injects If-Match when args.if_match() is set.
• s3_delete_objects propagates per-object if_match into the <ETag> field of the DeleteObjects XML body, so the batch path stays a single request even with conditional deletes.

CI:

• Add delete_with_if_match=false to OPENDAL_TEST_CAPABILITY_OVERRIDES in the four minio_s3* action.yml files

Tests:

• test_delete_with_if_match_match / _mismatch in core/tests/behavior/async_delete.rs.

Bindings:

• Node.js + Python DeleteOptions extended with if_match; Python pyi stubs and async/sync delete() signatures updated. .NET / Java / Haskell / Ruby / OCaml use ..Default::default() and need no changes.

Are there any user-facing changes?

Yes, additive only — op.delete_with(path).if_match(etag) is a new opt-in API. Existing op.delete(path) is unchanged.

AI Usage Statement

AI-assisted implementation.

[Xuanwo]

S3Deleter::delete_batch falls back to per-key delete_once whenever any entry in the batch carries if_match, since DeleteObjects v2 has no per-object If-Match slot. The non-conditional fast path is unchanged.

Seems to be wrong. There is no DeleteObjects v2 and DeleteObjects did support setting etag. For example:

POST /?delete HTTP/1.1
Host: Bucket.s3.amazonaws.com
x-amz-mfa: MFA
x-amz-request-payer: RequestPayer
x-amz-bypass-governance-retention: BypassGovernanceRetention
x-amz-expected-bucket-owner: ExpectedBucketOwner
x-amz-sdk-checksum-algorithm: ChecksumAlgorithm
<?xml version="1.0" encoding="UTF-8"?>
<Delete xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
   <Object>
      <ETag>string</ETag>
      <Key>string</Key>
      <LastModifiedTime>timestamp</LastModifiedTime>
      <Size>long</Size>
      <VersionId>string</VersionId>
   </Object>
   ...
   <Quiet>boolean</Quiet>
</Delete>

Please double check.

[YuangGao]

yes, I confused it with ListObjectsV2, just updated

• s3_delete_objects now writes op.if_match() into <ETag>
• Dropped the delete_once fallback in S3Deleter::delete_batch; the conditional batch path is a single request again.

[Xuanwo]

Please double check if minio support:

• copy_with_if_not_exists
• copy_with_if_match
• delete_with_if_match

[YuangGao]

Confirmed: MinIO community edition does not support delete_with_if_match — DeleteObject silently ignores If-Match and returns 204 (minio/minio#21677, maintainers: "this is a feature, not a bug, something new AWS added recently"). So delete_with_if_match=false is required here and will stay required regardless of MinIO version.

The other two (copy_with_if_not_exists, copy_with_if_match) are pre-existing overrides from #7600 — this PR doesn't touch them. They may be removable on a newer MinIO image (the wildcard * and 412/404 fixes landed after our pinned RELEASE.2024-09-22)