Fork storage utilization and reporting
<!--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=290226) </details> <!--IssueSummary end--> ### Problem to solve [Git object deduplication for forks](https://docs.gitlab.com/ee/development/git_object_deduplication.html) reduces storage costs and can improve forking speeds. How deduplicated repositories report disk utilization and how this applies to storage limits is not well defined. This creates problems like https://gitlab.com/gitlab-org/gitlab/-/issues/255001 ### Further details ### Proposal ### Links / references
issue