ci: skip md5 check if upload blobs have different md5 calculation strategy

Type of change

• Bug Fix
• Feature
• Pipeline
• Test

Does this introduce a change in the core logic?

• No
• Yes

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• GCP
• IBM

Does this follow conventional commits spec?

• No
• Yes

Have you set the target Milestone?

• No
• Yes

Have you set the no-detached-pipeline label?

• No
• Yes

Updates description?

Sdutil use incremental md5 calculation both upload and download the data, However other server (eg: segy) may not use same md5 calculation. Therefore, a false md5 mismatch could happened could happens when using sdutil to download the data.

If different md5 calculation has been detected, then sdutil will skip the md5 check and only print out a warning.