CompositeConfigurationNodes cacheKey can be incorrect

If a sub channel inherits everything from another channel including all its workspace nodes AND if the sub channel does not have any configuration of itself, then all the configuration nodes are the same, leading to the CacheKey of the CompositeConfigurationNodes to be the same for sub channel and the inherited channel

However, obviously, the sub channel has all its hst components inherited, and the primary channel doesn't. However, since the CacheKey is the same, the first that loads the hst components indicate whether they are inherited or not

Instead, we should include the root configuration node id in the cachekey to avoid incorrect reusage