FEAT: Fetch Followers and Display in a Dialog

[muntaxir4]

Is your feature request related to a problem? Please describe.
Currently, there is no functionality to fetch and display a user's followers dynamically. Users should be able to view a list of followers in a dialog, with each entry linking to the respective user’s profile. Endpoints affected /profile and /user/{handle}

Describe the solution you'd like

1. Implement an action flow (GET_USER_FOLLOWERS_START, GET_USER_FOLLOWERS_SUCCESS, GET_USER_FOLLOWERS_FAIL) to retrieve followers from Firestore.
2. Store followers data in the Redux store under profile.user.followers.
3. Display followers in a dialog, where:
   • Each follower is shown with their profile picture and display name and user handle.
   • Clicking on a follower redirects to their profile page, without relaod.
4. Show a loading state (with a loading button) while fetching the list.

Describe alternatives you've considered

• Fetching on every dialog open (less efficient than caching in Redux).

Additional context
This feature will enhance social interaction by allowing users to explore who follows them.

[rohitPandey469]

Nice one @muntaxir4 I was also working on it, was halfway through it #161
But you did it before me. Just one issue ig we are told not to repeat the issue and you should look beforehand creating an issue if its already raised by another contributor. As well as its a feature so multiple PR would have been acceptable so there wasnt a need. I will be raising a PR regarding it aswell, soon...

[muntaxir4]

Nice one @muntaxir4 I was also working on it, was halfway through it #161 But you did it before me. Just one issue ig we are told not to repeat the issue and you should look beforehand creating an issue if its already raised by another contributor. As well as its a feature so multiple PR would have been acceptable so there wasnt a need. I will be raising a PR regarding it aswell, soon...

Oh I didn't see that issue, probably you are only referring to the /profile page. And since, my approach was to make the UI for both endpoints similar #213 , the PR made them follow a consistency.