Added UI Component for Member_List of a server

[Hocng7]

Summary of Changes:

Introduces the implementation of the Member_List component, which is responsible for displaying a list of members within a server in the chat application. The component serves to enhance community interaction and facilitate communication among members.

Key Changes:

Member_List Component:

• The MemberList component is created to visualize the list of members within a server.
• It renders member names along with avatars in a visually appealing manner.

Hardcoded Data:

• Initially, hardcoded data for member names is provided to simulate the functionality.
  -This data can be later replaced with dynamic data fetched from the backend.

Page Structure (For ad-hoc testing purposes only):

• A dedicated page, Member_List Page, is introduced to host the Member_List component.
• The page encapsulates the Member_List component within a container for better organization.

Documentation:

• Comments within the code provide usage instructions and describe the purpose and features of the Member_List Page component.
• These comments aim to guide developers on the usage and functionality of the component.

Additional Considerations:

• The implementation focuses solely on the frontend presentation of the member list.
• Future iterations may involve dynamic data fetching from the backend to populate the member list.
• Consideration for responsive design and accessibility ensures usability across various devices and user demographics.
• This implementation lays the foundation for implementing the member list feature, providing a clear structure for further development and refinement.

[ColinLefter]

Great work! A UI placeholder is needed to integrate the functionality for the server member list, which is what will follow.

[ColinLefter]

Great work with setting out the layout for the server member list! This is a critical component as we need to differentiate friends that belong to an account versus members that belong in a server, and the UI will be similar. Implementing the hardcoded member now as part of this pull request is a great approach because we need to follow the process of constructing front-end components first and then integrating the backend. This is because if anything changes in the UI later on, we would have to undo all the backend functionality, so it is better if this is finalized first.

[ColinLefter]

Also, excellent outline for this pull request. Listing out the Summary of Changes, Key Changes, Documentation and Additional Considerations is a great format and is something that we should all adopt when we write our pull requests.