Add functionality to identify large repositories using existing project statistics data
## Problem Statement Currently, identifying large repositories (monorepos) in GitLab environments requires running Rails console commands or scraping through all projects via API. This is inefficient for administrators who need to check repository sizes, especially in the context of migrating from existing infrastructure to a new GitLab architecture. ## Current State GitLab already collects and displays repository size data in multiple places (Usage Quotas page or Project API) for single projects using `project_statistics.repository_size`. Data is pulled from Gitaly via [`app/models/project_statistics.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/2e95beb8fd6f71143b8c8d34b1b695420215fe84/app/models/project_statistics.rb#L66) and [`lib/gitlab/git/repository.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/2e95beb8fd6f71143b8c8d34b1b695420215fe84/lib/gitlab/git/repository.rb#L349) ## Proposal Reuse the existing `project_statistics.repository_size` data to provide administrators with easy access to large repository information through Admin UI Dashboard/Page by displaying a list of projects sorted by repository size with size >1GB: - Project name and path - Repository size (from `repository_size` field) - Total repository size (repository + LFS objects) - Link to project - Filtering and sorting capabilities Alternatively this can be done as Rake task, but UI would be more user friendly. Update - see note on https://gitlab.com/gitlab-org/gitlab/-/issues/578110#note_2843950599, MVC with rake output can be a good iteration to unblock folks. ## Related Documentation - [Large Monorepos Documentation](https://gitlab.com/help/user/project/repository/monorepos/_index) - [Reference Architecture large monorepos](https://docs.gitlab.com/administration/reference_architectures/#large-monorepos) - Related to analysis from https://gitlab.com/groups/gitlab-com/gl-infra/software-delivery/framework/-/epics/35
issue