Change Details

This diffs implements the same approach as Farcaster app, where invited users is listed in members tab and also fixes issue described in [ENG-11388](https://linear.app/comm/issue/ENG-11388/after-creating-the-farcaster-thread-with-user-which-receives-request). Note: This solution is not complete, there are two things left and I won't land this diff until addressing them: 1. There is one `TODO` later, I need to discuss with @tomek what is correct approach. 2. I found some places in the codebase where we rely on the fact that there are only two roles and logic relies on conditions like `!roleIsAdminRole(existingRole)` (which previously was truthy only for member, now also for invitieis) - after this need we need to update this and always check for the role we want

This diff implements the same approach as the Farcaster app, where invited users are listed in the members tab and also fixes the issue described in [ENG-11388](https://linear.app/comm/issue/ENG-11388/after-creating-the-farcaster-thread-with-user-which-receives-request). NOTE: This solution is not complete; there are two things left, and I won't land this diff until addressing them: 1. There is one `TODO` in this code, I need to discuss with @tomek what the correct approach is. 2. I found some places in the codebase where we rely on the fact that there are only two roles and logic relies on conditions like `!roleIsAdminRole(existingRole)` (which previously was truthy only for members, now also for invitees) - after this, we need to update this and always check for the role we want

This diffs implements the same approach as the Farcaster app, where invited users isare listed in the members tab and also fixes the issue described in [ENG-11388](https://linear.app/comm/issue/ENG-11388/after-creating-the-farcaster-thread-with-user-which-receives-request). Note:NOTE: This solution is not complete; there are two things left, there are two things left and I won't land this diff until addressing them: 1. There is one `TODO` laterin this code, I need to discuss with @tomek what isthe correct approach. is. 2. I found some places in the codebase where we rely on the fact that there are only two roles and logic relies on conditions like `!roleIsAdminRole(existingRole)` (which previously was truthy only for members, now also for invitees) - after this, now also for invitieis) - after this need we need to update this and always check for the role we want