Add 'List of Known/KYC'd Entities' use case

[dmitrizagidulin]

It would be helpful for the DCC/VC-Edu use case to be able to use the V.I.V. spec to map to our current 'issuer registry' use case.

The general idea is:
A client needs to be able to fetch a list of Issuers or Verifiers known by the registry host (by DID or other identifier).
For each entity (issuer/verifier etc), the metadata fields needed include:

• Entity name (e.g. "Example University")
• Entity Legal Name (sometimes different from entity name, e.g. "Board and Trustees of Example University")
• Website/homepage URL
• Logo URL (suitable for using in an <img src=...> field, so, either an https URL or an embedded data:image/... URL)
• An 'alsoKnownAs' like mapping of other identifiers the entity is known by. (For example, for the Example university, provide the ROR.org identifier for it, the CTDL identifier, the Bloomberg company ID, etc etc)

(See https://github.com/digitalcredentials/dcc-members-oidf?tab=readme-ov-file#get-fetchsubdid for an example of what's being used now).

[TallTed]

@dmitrizagidulin — The title of this issue (Add 'List of Known/KYC'd Entities' use case) doesn't make sense to me. Maybe that 'd should be 's? KYC'd is increasing my difficulty in making it make sense. Expand that to Know-Your-Customer'd and maybe you'll see a way to solve my struggle.