Consolidate Common Module Microservices

[Varaniya201]

As part of this technical feature implementation below design is being proposed where, commons will have only 2 packages within it which combines all the existing files/packages/ services:

1. kernel-core : This will contains below libraries/packages

• kernel-applicanttype-api
• https://github.com/mosip/commons/tree/v1.3.1-rc.1/kernel/kernel-dataaccess-hibernate
• kernel-datamapper-orika
• kernel-demographics-api
• kernel-idgenerator-machineid
• kernel-idgenerator-mispid
• kernel-idgenerator-partnerid
• kernel-idgenerator-prid
• kernel-idgenerator-tokenid
• kernel-idgenerator-vid
• kernel-idgenerator-regcenterid
• kernel-idgenerator-rid
• kernel-idvalidator-mispid
• kernel-idvalidator-prid
• kernel-idvalidator-rid
• kernel-idvalidator-uin
• kernel-idvalidator-vid
• kernel-licensekeygenerator-misp
• kernel-pdfgenerator
• kernel-websubclient-api
• kernel-transliteration-icu4j
• kernel-pinvalidator
• kernel-qrcodegenerator-zxing

2. kernel-service: This will contains below libraries/packages

• kernel-idgenerator-service
• kernel-notification-service
• kernel-pridgenerator-service
• kernel-ridgenerator-service

3. Removal of Spring dependency in kernel-core and remove kernel-bom
4. Below packages can be kept separately:

• kernel-config-server
• kernel-idobjectvalidator
• kernel-logger-logback
• kernel-templatemanager-velocity

5. Can we include otp-manager as part of commons instead of keeping it as separate repo?
6. prid generator is using the same logic of rid generator to generate aid. hence need to check on this and remove
7. salt-generator to be placed in the respective repos where it is used as job rather than service in commons