HDDS-13919. S3 Conditional Writes (PutObject) [3/3] - Remove expectedETag from OmKeyInfo

[peterxcli]

What changes were proposed in this pull request?

Found this while i was reviewing #10181

If-Match is handled on create using only KeyArgs: validateAndRewriteIfMatchAsExpectedGeneration checks the ETag against the DB key, then folds that into expectedDataGeneration and clears KeyArgs.expectedETag before prepareFileInfo. So OmKeyInfo never needed to carry the ETag; commit validation uses expectedDataGeneration only (see validateAtomicRewrite in OMKeyCommitRequest). The tests were already asserting openKeyInfo.getExpectedETag() == null.

What is the link to the Apache JIRA

• HDDS-13919. S3 Conditional Writes (PutObject) [2/3] - Reuse Atomic Rewrite at Commit Path #10023
• https://issues.apache.org/jira/browse/HDDS-13919

How was this patch tested?

existing tests

[peterxcli]

cc @YutaLin

[ivandika3]

Thanks @peterxcli , LGTM +1.

[peterxcli]

Thanks @ivandika3 for the review!