Gwen Auth/Data Custody

Description: We'll need some form of Auth for dweb hosting and Gwen. This will connect a user to an API key (once generated), to files, domains, form of payment, etc. This work will assist with persistence and data custody between apps (ex. contacts in Alberto + Gwen for the same account). Can create a registry for neighborhoods.

**As a user, I want my API key, files, domains, etc. to be linked to my account so that only I can access and manage them.**

- [ ] Should associate a login/account with their Gwen or Alberto assets:
- API Key (once generated)
- Files
- Domains
- Contacts
- [ ] Should only be able to be accessed by those that are authorized.
- [ ] Should be able to authenticate against the API.
- [ ] Should be demoed.

Notes:
- A lot of design to be done.
- Payment linkage will be separate ticket.
- Backend that could link to it. Need some way to link to the blockchain.
- Data custody. All data on the blockchain is public. Think more on this zkproofs or user-encrypted data.
- More details should be added.
- Auth token or passing API key as the Auth?

No files, tests, or entry points are identified in the issue. Start by resolving the authentication model, account-to-asset relationships, API authentication, authorization, and blockchain or data-custody approach; done should include a demonstrated implementation covering the listed assets.

Written by the indexing model from the issue text.