Fix healing of replication delete markers

[poornas]

A corner case can occur where delete marker was propagated but the
metadata could not be updated on primary. Sending a RemoveObject
call with the Delete marker version would end up permanently deleting
the version on target. Instead, perform a Stat on the DM
version on target and redo replication only if the DM is missing on
target.

Description

Motivation and Context

How to test this PR?

Need to synthetically induce error by skipping the metadata update in delete replication.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Optimization (provides speedup with no functional changes)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• Fixes a regression (If yes, please add commit-id or PR # here)
• Documentation updated
• Unit tests added/updated

[minio-trusted]

Mint Automation

Test	Result
mint-large-bucket.sh	✔️
mint-fs.sh	✔️
mint-gateway-s3.sh	✔️
mint-erasure.sh	✔️
mint-dist-erasure.sh	✔️
mint-gateway-nas.sh	✔️
mint-compress-encrypt-dist-erasure.sh	✔️
mint-pools.sh	✔️
Deleting image on docker hub
Deleting image locally