Teams

I figure this is probably something that either won't be offered or at least in a limited way for "free" users if that's a thing after the beta. But it's going to be a pretty immediate requirement even for a smaller team like mine.

A couple types of users/permissions I'd want to have:

- **Billing Account:**
- Manage Billing Settings
- **Admin Account:**
- Manage Secrets
- Manage Domains
- Manage Deployment Settings
- (All "Billing Account" settings)
- (All "Developer Account" settings)
- **Developer Account:**
- Trigger Deployments (using existing settings)
- (All "Read-only Account" settings)
- **Read-only Account:**
- View Analytics
- View Deployment History

No files, tests, or entry points are named. Start by reviewing the repository structure and existing account, team, or permission concepts, then compare them with the roles and capabilities listed in the issue. Done should include an agreed implementation scope for team roles and their permission boundaries.

Written by the indexing model from the issue text.