Changed CRC32C to MD5 to calculate a checksum (GONRG-5884)

Type of change

• Bug Fix
• Feature

Does this introduce a change in the core logic?

• [NO]

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

• AWS
• Azure
• GCP
• IBM

Does this introduce a breaking change?

• [NO]

What is the new/expected behavior?

Upgraded obm lib. look at osdu/platform/system/lib/cloud/gcp/os-core-lib-gcp!57 (merged). Changed an algorithm to generate check sum.

provider/storage-gcp/src/main/java/org/opengroup/osdu/storage/provider/gcp/web/repository/ObmStorage.java

@@ -35,6 +35,7 @@ import java.util.stream.Collectors;
 import lombok.RequiredArgsConstructor;
 import org.apache.commons.lang3.ArrayUtils;
 import org.apache.http.HttpStatus;
+import org.apache.tomcat.util.codec.binary.Base64;
 import org.opengroup.osdu.core.common.logging.JaxRsDpsLog;
 import org.opengroup.osdu.core.common.model.entitlements.Acl;
 import org.opengroup.osdu.core.common.model.entitlements.GroupInfo;
@@ -315,7 +316,7 @@ public class ObmStorage implements ICloudStorage {
         RecordMetadata updatedRecordMetadata = kv.getKey();
         RecordData recordData = kv.getValue();
         String recordHash = hashMap.get(updatedRecordMetadata.getId());
-
+        recordHash = new String(Base64.encodeBase64(recordHash.getBytes()));
         String newRecordStr = gson.toJson(recordData);
         byte[] bytes = newRecordStr.getBytes(StandardCharsets.UTF_8);
         String newHash = storage.getCalculatedChecksum(bytes);