store D1 configuration properties in the main backup so that they persist between upgrades.
update authoritative member node id when we change it (reconfiguration) and when we initially register as a MN with the CN.
new jars with many changes -- including new CN methods: ping, describe, listChecksumAlgorithm. Removed MN.setAccessPolicy. Refactored CN.setOwner() to CN.setRightsHolder().
configure synch schedule in the admin screenhttps://redmine.dataone.org/issues/1933
actually persist the MN id value to the properties file
set the newly assigned MN id after we call CN.register().
DataONE MN registration/configuration is now its own configuration page in the admin interface.http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5531