Follow-up from "Refactor counter implementations to be polymorphic"
<!--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=384117) </details> <!--IssueSummary end--> The following discussion from !104936 should be addressed: - [ ] @alberts-gitlab started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/104936#note_1188921340): (+1 comment) > I realized that this is still tied to `ProjectStatistics#increment_columns!`, which make the class unusable with other models that need counter. This seems to be a separate problem within ProjectStatistics though, where increment on one column has side effects on other columns. It should be tackled separately.
issue