Auto export should support a clustered setup

In a clustered setup it is reported that some system cnd's such hippo.cnd and hipposys.cnd are being exported. This is probably due to the reloading of these system cnd's during startup. In a non-clustered setup this loading of cnd's is performed before the export module is initialised. However in a clustered environment the second node can start up after auto export was already initialised on the first node.

A second issue involves the setting of the auto export location property in the repository. This property is always removed during shutdown of the auto export module. However the auto export plugin in the console looks at the location property to determine whether auto export is available. When the second node goes down, and removes the location property in the process, the auto export plugin in the first node thinks auto export is unavailable, preventing the user from enabling/disabling auto export.