Sorting namespace in the backend instead
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=334934) </details> <!--IssueSummary end--> In this MR > https://gitlab.com/gitlab-org/gitlab/-/merge_requests/65178, the ~frontend is manually sorting the data. As the response from the namespace request is unsorted. ![image](/uploads/336e54708d0fd0ecaf4f54fe3aa0b034/image.png) The question here is should the sorting happen on the ~backend instead (that way we will have a uniform and consistent data display throughout the app and the ~frontend won't have to worry about the adding an additional layer of sorting whenever we call fetch this data) However! maybe we want to keep the sorting on the ~frontend for the flexibility. There's a possibility that we may not want to sort it by `name` but instead `full_name`. So sorting on the ~frontend would give us this flexibility.
issue