Peer Contact Manager

[careck]

The idea of managing contacts is twofold:

1. Each identity has its own list of contacts for which it knows Name and Public Key.
2. When a workspace owner wants to invite a known contact to a new workspace, then it would refer to contacts from the identity contact list (address book?)
3. Each workspace has a list of peers which are participants in the sync of this workspace (excluding, of course, anonymous read-only peers in the case of .cloud broadcasts).
4. Some of the workspace peers will become known to the local identity because they have been invited by other peers to this workspace. They will then also be added to the identity's contact list.

This means that there are 3 lists of identities in the Krillnotes application:

1. Application wide: The list of local user identities (public and private keys), stored in the system config
2. Application wide: The list of known other contacts (public key and name), stored in the system config tied to an individual user identity. This list should also be encrypted on disk and be decrypted when the identity is unlocked.
3. Workspace only: The list of known peers of this workspace (public key and name), stored IN THE workspace.