SIP UUID generation

For the MDONS use case, we need to generate SIP UUID in both the T0 Multilayer topology and the T0 Full Multilayer topology using the method used for Node Edge points so that the resulting UUID are not random, and that we have a correspondance between both topology. In ONAP we use the T0 Multilayer topology which is abstracted. So service creation triggered from ONAP will use the SIP of this topology. But to convert the T-API service create into an OR compliant demand (handled through the Service Handler) we will rely on the T-API topology context in the MDSAL, so that we need a correspondance of the SIP maintained in this last, ortherwise we will not be able to make the conversion of the service request.

Acceptance criteria : the code is submited to review, does not bring regressions and the Junit test are adapted.