feat(organizations): fix data and navigation flow when member updates themselves TASK-1354

[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

The navigation and data flow is improved when an MMO organization admin removes itself from the organization.

📖 Description

The objective of this PR is to:

• Minimize wrong API calls due to permissions and session data that needs to be updated
• Present a better flow for the user, redirecting them to the correct view after the removal
  There's still a big margin for improving, mainly due to some work needed in useUsage, but it unfolds into several other files and flows, so it's better to be handled in a separated PR

👀 Preview steps

1. ℹ️ have an account and a project
2. Be the admin in an MMO
3. Navigate to Account Settings > Members
4. Remove yourself from the organization
5. 🔴 [on main] notice that the user is not redirected and there are some failed attempts to API calls due to permissions
6. 🟢 [on PR] notice that the user is redirected and there's only 1 failed attempt to usage API

[p2edwards]

Unrelated to this PR, but note to self: do we need to specify angle brackets here, or can we get better type safety and readability by leaving this blank and fixing types upstream of it?

• 📚 reference: "Type-safe React Query # About angle brackets"

[p2edwards]

Skimmed, will test soon.