Description
introduce central registry of well-known consumer identity types

• that are shared by credential graph, plugin manager and plugin implementations
• this allows normalizing aliases and type fields

TBD:

• decide on dymanic consumer identity system based on json schemas (main issue here is overlapping identities)
• rename consumer identity type to consumer type

Schedule a design session! We need to discuss how we evolve this (we probably do not want to start with the fully fledged dynamic registration solution, but we need to know how it will look like, the plan the path towards that!)

Done Criteria

• Code has been reviewed by other team members
• Analysis of existing tests (Unit and Integration)
• Unit Tests created for new code or existing Unit Tests updated
• Integration Test Suite updated (includes deletion of existing unnecessary Integration Test and/or creation of new ones if required)
• Enduser Documentation updated (if applicable)
• Internal technical Documentation created/updated (if applicable)
• Successful demonstration in Review