Initial version of the unique ID generator

1. The UID service is deployed in SKAMPI. 2. The UID service returns the UID as defined in the specification (Insert here an unambiguous specification that applies to the UID service, refer section above section for documenting requirements. Even if documented requirements include eventual functionality or performance, we can indicate which requirements are fully addressed by SP-920 , which are not, and or to what level of performance SP-920 addresses others). 3. A library is published via which using code can query the UID service. 4. System level test: SDP scan ID is from from UID service 4.1 There a test set in SKAMPI that addresses testing a System Under Test (SUT) comprised of 2 or 3 components/services: the OET, the UID service, and the SDP sub-array node (TBC, but the idea is that the scan UID as generated by the UID service needs to be traced right through to the SDP). 4.2 The test cases exercise the SUT so that all the involved components/services are exercised. 4.3 The test cases address key capabilities or requirements that are relevant to the specific SUT: in this case, unicity, speed of delivery / response time (~100ms acceptable, with a target of 50ms) and expected format. Note: Due to uncertainties, in the short term, measurement of performance is much more important than the actual performance measured. 4.4 The test set is regularly run within the CICD, in an appropriate stage called "integration tests".