Add Organizations' User Invitation UI

[yasinelmi]

Summary

Implements the frontend for #6088: a My Organizations landing page, an organization
edit page with Details and Sharing tabs (invite/manage members), and organization
creation — following the existing channel edit/details page pattern.

Closes #6088

New pages and features

Description	Screenshot
My Organizations landing page — reached via the new "My organizations" nav tab. Shows a banner of pending organization invitations (accept/decline) above a card grid of the organizations you belong to, each showing your role in it.
Organization card options menu — the "⋮" button on each card opens a dropdown with "Edit organization," which goes to the same edit page as clicking the card body.
New organization form — reached via "New organization" on the landing page. Same page/component as editing an existing org, just blank, with no tabs (nothing to share yet) and a "Create organization" button instead of "Save changes." The creator automatically becomes the org's admin.
Organization edit page — Details tab (as admin) — name/description/public checkbox, editable. Header uses the same dark "immersive modal" banner as the channel details page, including its focus trap and Escape-to-close behavior.
Organization edit page — Details tab (as a non-admin member) — same page, but fields are disabled with an explanatory notice ("Only organization admins can edit these details") instead of silently failing on save.
Sharing tab — invite + manage members — only visible to org admins. An invite-by-email form with a role selector (Viewer/Editor/Admin), plus a single table unifying active members and pending invitations, each with a "⋮" menu (role change / remove for members; resend / revoke for pending invites).
Sharing tab — as a non-admin — replaced entirely with a "Only organization admins can manage sharing settings" message; no invite form or member table rendered at all.
Remove-member / revoke-invitation confirmation — both are destructive actions gated behind a confirmation modal naming the affected email.
Last-active-admin protection — the API refuses to demote, deactivate, or remove an organization's only active admin; the UI surfaces the exact server error as a snackbar instead of failing silently.

Framework compliance (per the issue's Frameworks checklist)

• No Vuetify anywhere in the new code — every component uses Kolibri Design System
  (KCard, KButton, KTextbox, KCheckbox, KSelect, KTable, KTabsList,
  KModal, KDropdownMenu, StudioImmersiveModal).
• No Vuex — all new state is Composition API composables
  (useOrganization, useOrganizationList, useOrganizationMembers,
  useOrganizationInvitations).

Accessibility

• Every icon-only button has an ariaLabel/tooltip, each carrying a per-item
  distinguishing label rather than a generic repeated one — e.g. "More options for
  {org name}" on organization cards, "Options for {email}" on each row of the
  members/invitations table, and "Accept/Decline invitation to {organization}" on
  each pending-invitation banner entry.
• Keyboard focus is trapped inside the edit page while open (via StudioImmersiveModal's
  KFocusTrap), with Escape closing it — matching the existing channel details page.
• The document/tab title updates on every route and tab change, so screen readers get a
  cue that the SPA navigated even though there's no real page reload.
• Disabled form fields for non-admins are paired with visible explanatory text, not just
  a visual dimming.

Test plan

• pytest — organization, organization-role-annotation, and invitation tests pass
  (102 backend tests)
• pnpm test — full channelList frontend suite passes (226 tests)
• pre-commit run --all-files on all touched files
• Manually verified in the browser: invitation accept/decline, invite-by-email, role
  changes, resend/revoke invites, member removal (including the last-active-admin
  guard), organization creation, and the non-admin read-only states

Notes for reviewers

• No Vuex and no Vuetify anywhere in the new code (all new state is Composition API
  composables) per the issue's Frameworks requirements.

🤖 Generated with Claude Code

[learning-equality-bot]

👋 Hi @yasinelmi, thanks for contributing!

For the review process to begin, please verify that the following is satisfied:

• Contribution is aligned with our contributing guidelines

• Pull request description has correctly filled AI usage section & follows our AI guidance:

  AI guidance

  
  

  State explicitly whether you didn't use or used AI & how.

  If you used it, ensure that the PR is aligned with Using AI as well as our DEEP framework. DEEP asks you:

  • Disclose — Be open about when you've used AI for support.
  • Engage critically — Question what is generated. Review code for correctness and unnecessary complexity.
  • Edit — Review and refine AI output. Remove unnecessary code and verify it still works after your edits.
  • Process sharing — Explain how you used the AI so others can learn.

  
  

  Examples of good disclosures:

  "I used Claude Code to implement the component, prompting it to follow the pattern in ComponentX. I reviewed the generated code, removed unnecessary error handling, and verified the tests pass."

  "I brainstormed the approach with Gemini, then had it write failing tests for the feature. After reviewing the tests, I used Claude Code to generate the implementation. I refactored the output to reduce verbosity and ran the full test suite."

Also check that issue requirements are satisfied & you ran pre-commit locally.

Pull requests that don't follow the guidelines will be closed.

Reviewer assignment can take up to 2 weeks.