Draft: Move organizations to new /o/ path
What does this MR do and why?
This change reorganizes how organization URLs are structured. Previously, all organization-related pages used a single URL pattern, but now they're split into two different approaches: general organization pages (like the list of all organizations) use a "/-/organizations" path, while individual organization pages use a shorter "/o/" format.
I'm proposing that we keep the index and new actions at the existing path, because /o/new and o feel ambiguous. The other advantage to leaving the index action at /-/organizations for now is we don't have a concern about self-managed instances having a potential conflicting group or username. We will still need to address this as part of #553144 (closed) before rollout to self-managed customers.
References
Screenshots or screen recordings
| Before | After |
|---|---|
 |
 |
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.