fix(organization)!: restrict invite details to the user's current organization TASK-1590

[rajpatel24]

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

Updated the members API endpoint to ensure invite details are only available for the organization a user currently belongs to.

📖 Description

Previously, the members API endpoint could display invite details from a user's past organization, even after they joined a new one. This update ensures that:

• Invite details are only shown if the user is still part of the organization.
• If a user is removed from an organization, their invite details for that organization will no longer be visible.
• If the user joins a different organization, invite details from the previous organization will not be carried over.

This change improves data consistency and ensures that invite details are relevant only within the organization where the user is currently a member.

[noliveleger]

LGTM