Don't (auto)export of jcr:uuid values based in HCM group "hippo-cms" (aka core, or product) configuration

For many/most use-cases exporting product based jcr:uuid properties is not needed, nor desired.

AutoExporting these properties (on first detected 'change' or addition) in an end project
(which for example might be triggered by adding a property to the / root node)
can lead to 40+ changes and new yaml configuration files, just for the jcr:uuid properties alone.

As a quick fix (this might be resolved differently before the final v12 GA) we simply will suppress exporting jcr:uuid properties for nodes which are based (first defined) in the group "hippo-cms", meaning, defined by the product itself.

Other jcr:uuid properties for nodes created by an end project will remain being exported.