Metacat

share the same dbConnection when inserting and then updating SystemMetadata objects in the backing store.
any errors encountered during the update will rollback the entire transaction and the SM record will not exist, even in part.

Do not loadAllKeys() for SystemMetadataMap when Metacat first starts up. hzIdentifiers will be populated with a simple SQL statement rather than the serial loading of every single SystemMetadata object. It will remain in synch using the usual entryXXX() methods as before....

only generate system metadata for original objects.
https://redmine.dataone.org/issues/2721

add comment about returning early when no system metadata can be found.
removed extraneous check on the content type of the SM -- was unused.
formatted indenting

for SystemMetadata events we first check the event for the SM value. If it returns null, we look it up from the shared map. It seems as if we don't always get a value with our events.

comment out: synchronize local system metadata on cn restart

synchronize local system metadata on cn restart

log calls to store() system metadata to the backing store

Add the listener for LifecycleEvent state changes

synchronizeLocalStore() when the cluster has a LifecycleEvent state change to RESUMED.