When creating a ResourceFacingServiceSpecification the kubernetes related fields of the resource specification are not propagated to the parent ResourceFacingServiceSpecification

This is needed for example when we are creating a ResourceFacingServiceSpecification based on a CRD. The fields need to be propagated to parent ResourceFacingServiceSpecification The issue is an implication of #20 (closed)

It seems that the characteristics of a Resource spec child must be copied, so the change need to be reverted