feat(ChatRoom): Display Group Members' Names

[Bittukr7479]

Is your feature request related to a problem? Please describe.
Yes, this feature will address the need to display the names of group members in a well-organized and visually appealing format, improving the overall user experience. Currently, users may struggle to view or identify group members effectively, which impacts usability

Describe the solution you'd like
I would like to implement a UI feature that displays a list of group members:

• A title (e.g., "Group Members") with a group icon for better context.
• Each member's name should appear with a serial number (e.g., "1. John Doe").
• Responsive styling to ensure compatibility with different devices and screen sizes.
• Optional enhancements for future use cases, such as highlighting selected members or showing additional details like roles or activity status.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Approach to be followed (optional)
A clear and concise description of approach to be followed.

Additional context
Add any other context or screenshots about the feature request here.
Before:

After:
https://github.com/user-attachments/assets/36eb9fc7-2a3d-46d4-8906-05d3f1170161

Potential internship candidates

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

• Student Internship Programs talawa#359

[palisadoes]

We are now focusing on three types of issues as priority areas:

1. The improvement in the reliability of our code base. There are many issues created to test existing code. It is a good place to start if you want to understand the operation of various apps. When you submit PRs, we automatically check to see whether the code you submitted has been covered by testing and that each file meets the minimum standard level of the repository as a whole. You won’t be able to avoid understanding testing regimes to contribute to Talawa.
2. The fixing of bugs and features that seriously hamper the user from using the application. The apps have various shortcomings. The most obvious ones are where the apps do not work as expected. For example buttons that don’t work, errors or messages that are not displayed to make the user understand what to do and many more. Think of any difficulty you have had in getting things working, there could be a bug there waiting for you.
3. Coding of screens for issues created by our Contributor team based on our soon to be updated design guide. This may include updates to existing screens.
4. The creation of additional or updated documentation that helps with improving both the experience of the end user and the various GitHub contributors who support the development of our software. This would include user guides.

We will only be accepting feature issues for deficiencies that are obviously lacking in the apps. These are things that make it very difficult to operate the apps. Even so, the PRs will still require you to understand testing as stated before.

Cosmetic changes that require only a few lines of code, or relate to screen sizes unlikely to be used are not acceptable under this policy.

Closing