feat(organizations): remove mmos feature flag TASK-1397

[pauloamorimbr]

🗒️ 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

Now the Organizations feature implemented up to this point is no longer hidden behind a feature flag

📖 Description

• isMMosEnabled feature flag was removed
• routes and menus hidden behind it are now enabled by default
• organizationQuery no longer returns fixed result for is_mmo

👀 Preview steps

Feature/no-change template:

1. ℹ️ have account
2. ℹ️ have or be part of an organization
3. ℹ️ Make sure to disable the active feature flag with ?ff_isMMosEnabled=false or cleaning your session storage
4. Navigate to account settings
5. 🟢 notice that the organization links are visible
6. 🟢 notice that you can navigate and operate organization feature freely without the feature flag

[jamesrkiger]

Just a style issue: I tend to think we should move all the doc text for fetchOrganization above it. It's essentially a single line of code broken for screen length purposes. Seeing that solo await without brackets around it feels weird.

[p2edwards]

So, combining both comments... Revisiting the existing comment above fetchOrganization, seems if we're removing the feature flag, we can simplify it even more by putting fetchGet<...> into queryFn below

[pauloamorimbr]

Thank you...nice catch. I visually ignored those comments and should've just removed everything at once. Just did it now. Also some changes to the query were required due to dependencies, since now we're using the organizationUrl inside of the query.

[jamesrkiger]

left one minor comment on style, lgtm otherwise