Replace MD5 hash for lineage graph

To support FIPS, we have to use FIPS-approved algorithms. In front end, we use MD5 hash algorithms to generate query hash for lineage graph. But MD5 is one of forbidden algorithms for FIPS. We have to replace MD5 with FIPS-approved algorithm, or non-cryptographic hash function like murmur3_128. 

We might need to figure out if there are external dependencies on the hash. e.g. the lineage graph was consumed by other component services, like Apache Atlas, and maybe they somehow rely on the hash being consistent across versions (seems unlikely).