Metacat

In the MN.updateSystemMetadata method, when we set the obsoletedBy and obsoletes method, we will check if those values already exist in other chains.

Add the identifier in the message of the exception when a client tries to reset the obsoletes or obsoletedBy fields.

Check the obosoletedBy and Obsoletes only can be set once.

The method of setReplicationstatus can be called by CNs and MNs.

merge from V2 impl: check for optional "failure" param instead of throwing exception when it is missing (often is). https://redmine.dataone.org/issues/7283

check for optional "failure" param instead of throwing exception when it is missing (often is). https://redmine.dataone.org/issues/7283

Fixed a possible null pointer exception bug. https://redmine.dataone.org/issues/7280

Only CNs can call those methods:
CNCore.registerSystemMetadata()
CNCore,updateSystemMetadata()
CNReplication.setReplicationStatus()
CNReplication.updateReplicationMetadata()
CNReplication.deleteReplicationMetadata()

On mn.update and mn.updateSystemMetadata, those clients are allowed:
1. CNs.
2. Clients with appropriate permission calling the method on the authoritative nodes.

When compare the dateUploaded, now we use sysmetadata.getDateUploaded().getTime(). It used systemmetadata.getDateUploaded() (Date objects) to compare.