feat(organizations): account sidenav update for MMOs TASK-977

[jamesrkiger]

🗒️ Checklist

1. run linter locally
2. update all related docs (API, README, inline, etc.), if any
3. draft PR with a title <type>(<scope>)<!>: <title> TASK-1234
4. tag PR: at least frontend or backend unless it's global
5. fill in the template below and delete template comments
6. review thyself: read the diff and repro the preview as written
7. open PR & confirm that CI passes
8. request reviewers, if needed
9. delete this section before merging

📣 Summary

Handle MMO and non-MMO orgs, as well as org roles, in the account sidebar.

👀 Preview steps

Based on figma designs here

Requires MMO feature flag

1. Create a user and check to ensure account sidenav remains unchanged on Stripe-enabled and disabled environments. The should be no changes for users who are not members of an MMO.
2. Make user's org an MMO, with them as an owner, and check the sidenav with Stripe enabled and disabled against the Figma designs for org owners.
3. Create another user and add them to the MMO (make sure to delete their personal org). Make them an admin and check against the figma designs as above.
4. Make second user a member (uncheck "admin" on their org user object in django admin) and check against the figma designs as above.
5. Toggle the use_team_label option in constance and see organization/team label change accordingly in sidenav.

[notion-workspace]

Account Routing and Sidenav

[pauloamorimbr]

Noob question: Don't you also need to push the files generated by the script? Or didn't you need to run the generator for this one?

[jamesrkiger]

@pauloamorimbr Nope, not necessary since the script gets run on install.