Problem

When we introduce the advanced segment mid with included hash this was also adopted for the transit file parser. Because of lack of testing data, we where not able to test the implementation. 

The mid is generated out of the segment id parsed from the file and the file name. On export, the code expects the mid calculated for the source segment to be the same as the one on the target segment. But since soure and target are coming from 2 different files, the mids for those segments have different values (because of different file name).

Sine this file format is not standard xliff we will remove the "hash" type mid and use the old way of parsing and setting this value (from parsed segment id from the file).