Currently DefaultCacheManager explicitly starts CacheManagerJmxRegistration before calling ModuleLifecycle#cacheManagerStarting, which means MBeans in other modules are not registered in JMX.

We should start CacheManagerJmxRegistration only during global component registry start, after the modules have registered their components. If we want to make the cache manager available in JMX before DefaultCacheManager.start(), we should only register that particular MBean. Conversely, on shutdown, components other than the cache manager should be removed from JMX on DefaultCacheManager.stop() (as per ISPN-118).