Repository class growing too complex

[deusebio]

While developing I started to face a couple of warnings, linting errors related to the fact that the Repository class is growing too big. In particular:

• We are very close to having 20 public methods, which is the limit
• The test file is becoming larger than 1000 lines (to resolve this issue I have now temporarily disabled this lint the C0302 check)

We should identify a sensible choice for splitting the class, possibly either by function (tag, pull_request, branch_ops) or by resource (differentiating the functions that pertain to the local repo vs the one for the remote one)