Remove repository wrapper

[Xela101]

New Pull Request Submissions:

1. Have you followed the guidelines in our Contributing document?
2. Have you checked to ensure there aren't other open Pull Requests for the same update/change?
3. I have added tests to cover my changes.
4. All new and existing tests passed.
5. Have you lint your code locally prior to submission?
6. Does your code follows the code style of this project?
7. Does your change require a change to the documentation.
   • I have updated the documentation accordingly.
8. Have you added an explanation of what your changes do and why you'd like us to include them?
9. Have you inserted a keyword and link to the issues the PR closes in its descriptions (ex closes #1) ?
10. Is you branch up to date, have you integrated all the latest changes from develop and resolved conflicts ?

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  Enhancement
• What is the current behaviour? (You can also link to an open issue here)
  Repositories use the RepositoryWrapper
• What is the new behaviour (if this is a feature change)?
  Repositories use their custom repository implementation and are now isolated from RestSharp, you can no longer directly query the underling RestSharp repository making it easier to test custom queries.
• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
  Yes, new methods have been added to the Custom repositories to isolate themselves from the underling Repository.
• Other information:
  closes Remove repository wrapper #1108

[JayArrowz]

The full IRepository pattern is not exposed to the user, hence they are limited to the Repository interface methods in the Catalyst code (IPeerRepository, IMempoolRepository, etc..) instead of the actual IRepository<T, TKey> methods. (Not sure if this was the original intent)

The Repository Wrapper was exposing all the methods of the IRepository<T, TKey> this saves the developer having to write out new methods inside the interfaces (IPeerRepository, IMempoolRepository, etc..) when they are not fully exposed. And it looks like the wrapping behavior is still there, the only difference is less methods are accessible.

public PeerRepository(IRepository<Peer, string> repository)
        {
            _repository = repository;
        }

Edit: I can also see that we loose the ability to use the IQueryable pattern unless its exposed.

[JayArrowz]

You can do it this way but then you'll need to modify this (because it is populating them inside the container using reflection and not checking if base interface is IRepository):
https://github.com/SharpRepository/SharpRepository/blob/34c910bdf480d40cf5f8ea525960d4caeaca54f6/SharpRepository.Ioc.Autofac/RepositoryRegistrationSource.cs

Suggested change

	public interface IPeerRepository
	public interface IPeerRepository : IRepository<Peer, string>

Only benefit from this is that you wont get IRepository<Peer, string> all over the code and you can use the IRepository functions.

[Xela101]

Yeah, I have talked with James a few days ago about it and how the Wrapper works by allowing you to use the full repository functionality and think we are going to only allow users to construct their own specific methods and limit direct querying. It should hopefully allow for better code reuse and testing. I think now these Specific Repositories could be renamed Services since it is pretty much the repository-service pattern.