HstComponentConsfiguration must become aware whether they are inherited from a 'common' configuration or not

The template composer should by default not be able to modify inherited configuration. For example assume:

hst:configurations
common
siteA
siteB

if siteA and siteB both inherit from common, then the template composer for siteA should not be able to change hst:containercomponents from the inherited common. We can disable these hst:containercomponents in the template composer if we have this information somehow available that the container is inherited from another configuration