API - Deprecate the Group Chats for Events Feature

[palisadoes]

Is your feature request related to a problem? Please describe.

To simplify the UI/UX we have decided to deprecate group chats tied to Events so that the draft GSoC 2024 chat idea just focuses on creating basic expected functionality.

The link to chats was previously removed from the bottom of the app’s screen because of this lack of functionality. All other chat code remains.

Describe the solution you'd like

This means that all support for this feature must be removed. This includes removing all of the following related items:

1. Underlying code related to the specific support of this feature
2. Any testing code specific to this feature

All other code related to group chats must remain. We only want the group chat feature related to Events to be removed.

Describe alternatives you've considered

• N/A

Approach to be followed (optional)

• N/A

Additional context
The Figma designs showing the relevant Event Group Chat screens can be found here:

• https://docs.talawa.io/docs/design/ux/ux-design-system

Other
Issues related to this issue include:

• Mobile - Deprecate the Group Chats for Events Feature talawa#2297
• API - Deprecate the Group Chats for Events Feature #1618

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

• Student Internship Programs talawa#359

[pateldivyesh1323]

I would like to work on this.

[karankulshrestha]

I love to work on this.

[pateldivyesh1323]

@palisadoes I have visited whole codebase, and according to that there are currently no traces of code which is related to Group Chats for Events.

[pateldivyesh1323]

@palisadoes I have visited whole codebase, and according to that there are currently no traces of code which is related to Group Chats for Events.

@palisadoes Can I know your view on this?

[palisadoes]

1. The original design aim was that the invitees to an event would automatically be made part of a chat group.
2. If that is the case we should close this issue. This was done as a precaution.
3. Closing