Avoid MD5 hash for data file path of IcebergTable

To support FIPS, all new code have to use FIPS-approved algorithms. Current code generate data path hash in MD5 hash for Iceberg Table. But MD5 is one of forbidden algorithms for FIPS. Even for non-security purposes, like hash map, we still cannot use MD5  since CryptoComply libraries have no way to distinguish between hash function being used for non-security purposes versus security purposes. We have to get rid of the md5 in Iceberg table related code.