Propagate value type, when copying characteristics to RFS from supporting resources
# Importance of enhancement Since secret management integration (https://labs.etsi.org/rep/groups/osl/code/-/work_items/36), underlying controllers (e.g., CRIDGE) can create resources with secret characteristics. The value type of resource characteristics is correctly captured (https://labs.etsi.org/rep/osl/code/org.etsi.osl.model.tmf/-/work_items/33), and therefore sensored, but when the characteristics of all the supporting resources are copied to the overlay RFS ([code](https://labs.etsi.org/rep/osl/code/org.etsi.osl.tmf.api/-/blob/develop/src/main/java/org/etsi/osl/tmf/sim638/service/ServiceRepoService.java?ref_type=heads#L1233)), the value type is not taken into consideration. Currently, the propagated overlay service characteristics cannot be checked (and sensored), even if they are secret. # Enhancement description Also propagate the value type, along with the value copying of the characteristics of the underlying resources. # Definition of Done (DoD) - A CRIDGE-related RFS must also include the valueType in the copied characteristics
issue