JGroupsTransport leaks channel after initial cluster size timeout

JGroupsTransport fails during startup if a minimum cluster size is configured and there are not enough nodes. Because the component is in failed, stopping the cache manager does not invoke the stop method and the channel is leaked.

We could catch the exception in JGroupsTransport and close the channel there, but it would be safer if BasicComponentRegistryImpl invoked the stop methods for failed components as well.