fix: fixed the app's behavior in read-only channels.

[Spiral-Memory]

Brief Title

Fixed the issue where, in read-only channels, users with posting permissions can now send messages as usual. However, those users without permission to post can still read messages but are restricted from sending messages to the group. They will be notified that the group is read-only, ensuring appropriate behavior.

Acceptance Criteria fulfillment

• Fetched the permissions for posting in read-only from the permission API, as mentioned in the Rocket Chat REST API docs, using the endpoint: /api/v1/permissions.listAll.
• Retrieved the user's permissions using already defined function getChannelRoles() for the channel and determined the permissions of the logged-in user.
• Compared the user's role with those who are permitted for posting in read-only.
• Once verified, set a state in the userStore indicating whether the user is allowed to send messages in a read-only group.
• Utilized that state to render whether the room is read-only and disabled the message box accordingly.
• Logout the user with appropriate message when channel is private and user is not permitted.

Fixes #420

Video/Screenshots

2024-01-23.18-45-21.mp4

Note: This PR changes the backend code and requires a rebuild.

[Spiral-Memory]

Hey @abhinavkrin , I have made the required changes, and the PR is now ready for review. I am also attaching a video demonstrating the behavior of all possible permutations of non-private-non-read-only channels, non-private but read-only channels, private but not read-only channels, and both private and read-only channels. In all cases, the behavior is now appropriate, addressing all the issues I mentioned earlier. This PR deals with disabling writing to read-only channels if not permitted and showing the same info. Additionally, logout any user if the channel is private and they are not permitted, with a valid toast message.

2024-02-08.01-03-42.mp4

Note: In the video, [email protected] is the authorized user and [email protected] is the unauthorized user. This is to demonstrate the functionality of the app.

[abhinavkrin]

@Spiral-Memory Please resolve merge conflicts

[Spiral-Memory]

@Spiral-Memory Please resolve merge conflicts

Yes Sure @abhinavkrin

[Spiral-Memory]

@abhinavkrin, I have resolved the conflicts, please check now.