CSPACE-6262: Reduced a routinely-encountered log message from WARN to TRACE level.
CSPACE-6308: Don't blank out computed current location value in a Cataloging record if the most recent movement has a blank current location value.
CSPACE-6307: Use updatedAt, rather than createdAt, as tiebreaker when identifying the latest L/M/I record for maintaining the computed current location value in Cataloging records.
CSPACE-6307: Fix trivial typo in comment.
CSPACE-6188: Provisional XmlReplay-based tests to identify if the update computed current location batch job works as expected in a versioning tenant.
CSPACE-6188: Added missing auth credentials to XmlReplay-based test.
CSPACE-6188: Added (commented out) entry for running tests to verify that the batch job that updates computed current locations in Cataloging / CollectionObject records works with versioned records, to the XmlReplay master file.
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.
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 branch 'ucb-deploy_4.0' into botgarden_4.0