[czpython]

A team is a named group of people with a list of apps. This change stores teams and lets an admin manage them. It changes no access: every account still uses every app as before.

Backend

• A new package, druks.teams. A team joins people and apps, so it sits above druks.accounts and the app loader, and druks.accounts does not change.
• Team: a unique name, its member accounts, and a list of app names. Two new tables, teams and team_members.
• GET, POST /api/teams and PUT, DELETE /api/teams/{team_id}. The admin gate is a dependency on the router, so each route is admin only, the list also. Create and replace take the same body: the name, the member account ids, and the app names.
• A member must be an operator account. An app must be installed and not built in. Two teams cannot have the same name. Each refusal answers 422 with the reason.
• Deleting a team removes its memberships and no account.

Platform

• druks.exceptions.ValidationError: one error for input that Druks refuses. The server answers 422 with its message, so a route catches nothing.
• Model.get and Model.get_or_none take an optional session as the first argument. Platform code passes its session, and an app leaves it out. A miss on get answers 404 as before.

Dashboard

• A Teams section in Settings, in the Organization group after People, for admins only. It lists each team with its people and apps, and an admin can add, edit and delete a team.
• The form picks people and apps with the same switch rows that app options use.