Follow-up from "Add new method for RepositoryInfo RPC"
<!--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=416526)
</details>
<!--IssueSummary end-->
The following discussion from !124473 should be addressed:
- [ ] @vyaklushin started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/124473#note_1449506043): (+3 comments)
> **Question** I noticed that we mock the response in other tests. Should also return a double here and do a real call to Gitaly one level up in `git/repository_spec.rb`?
### Question
Should we use mocks in gitaly services tests or not? ([an example](https://gitlab.com/gitlab-org/gitlab/blob/4cffc6225aa7c1cc0fc15f4c94d075a8de9998a1/spec/lib/gitlab/gitaly_client/repository_service_spec.rb#L18)).
### Proposal
We should make a decision and enforce a consistent style across the codebase.
issue