CSPACE-6129: When computing a Cataloging record's current location from related L/M/I (Movement) records, if two or more such records have identical location dates, use their update timestamps as a tiebreaker.
Merge pull request #142 from aronr/CSPACE-6129

CSPACE-6129: When computing a Cataloging record's current location from ...
CSPACE-6129: Added (commented out) entry to the XmlReplay master file, for running tests to verify that the batch job that updates computed current locations in Cataloging / CollectionObject records uses the updatedAt timestamps for related L/M/I records as tiebreakers, when two or more L/M/I records share the same location date.
CSPACE-6134: In the batch job that updates computed current locations in Cataloging / CollectionObject records, verify that related L/M/I records with null current locations can't 'null out' existing computed current locations. Add verification that candidate current locations can be successfully parsed as refNames.
Merge pull request #143 from aronr/CSPACE-6134

CSPACE-6134: In the batch job that updates computed current locations in...