[UX] Presenting multiple data registries to the user (mostly label)

I marked it as UX since minor lacks in specification affect it.

Short recap of current state:

• each user can have multiple storages
• each storage can have multiple data registries (should we reconsider?)
• each data registry can have only one data registration for a given shape tree

We can use Shape Tree Descriptions to present the data registration.
What we lack is presenting the data registry, all owned the end user and all owned by each social agent who shares data with the end-user.

Having one data registry per storage can help, since presenting storage would be sufficient to identify the data registry.
There is also the case of data registries owned by other social agents, we need to make sure that user which received access to some data in them can have those registries labeled e.g.

• ACME has regional storages
• ACME shares project with Alice from NA and EU storage (data registry), it includes permission to create new project
• Alice wants to create new project specifically in NA storage

Start by reading the issue's Shape Tree Descriptions link and the repository's specification material. Clarify how data registries owned by the user and by sharing social agents should be identified, especially for ACME's regional storages. Done requires an agreed presentation and labeling specification for the described access scenario.