Ithaca increase test coverage and fix tzstats

[vkresch]

Changelog:

• Test reactivation
• API consistency test so that tzstats = rpc = tzkt
• Reward API cached data update
• Fix tzstats reward api
• Fix rpc reward api

Resolves #600

To fix tzstats I am currently assuming since tzkt api is working it is the standard to which we should compare values for now.

Notes:
I readded some tests with actual API calls. I think the best way to currently test TRD is a mix between real and mock API calls.
With real API calls we can detect faster deprecated API endpoints IMO thus we can adjust/fix things quicker. The real API calls should only do non changing data calls. That means we call only data which is static and can never change e.g. the balance in the past cycles. I know it slows down the merge process and that there is a discussion about mocking all the API calls but that way we can make sure TRD works.

Mock API calls we should use if we want to test some recent data which will change in the future. E.g. the current balance of a delegator or the data is to big to query each time (performance issue).

IMPORTANT:
Please use in future PRs:
@pytest.mark.skip(reason="no way of currently testing this")
if you really need to disable a test instead of removing or commenting it out.
Also provide a reason for that for future developers who do not know why the test was disabled.

Issues detected during test activation (tick means this PR solved this issue):

• Querying the baking rights via pRPC causes currently a 429 To many requests error. I created an issue at the tezos repo (https://gitlab.com/tezos/tezos/-/issues/3791). Let me know if this is the right place to post the issue.
• RPC reward API did not filter out zero staking balance delegates
• Updated potential_endorsement_rewards of tzstats by divinding with 1e6 to approximatly match tzkt futureRewards

Work effort: 32h

[nicolasochem]

Thanks, the suggestion to use a mix of mock and real rpc calls makes sense. Also, I'll make sure to skip the pytest tests instead of commenting them out.

[vkresch]

Need to implement some final tests for the reward api of tzstats and then the PR can be reviewed and merged.

[vkresch]

@nicolasochem @jdsika can you both test the the tzstats reward api? I would like to merge this PR as soon as possible because it's getting to big. Thanks!

I still did not removed the release_override and currently there are issues with rpc which do not match with tzkt but that will be for another PR.

[jdsika]

@vkresch I think you should have a look at your tests and then we can test it, right? I will be more active now and push a release

[jdsika]

@vkresch please make sure this gets ready this week!

[vkresch]

@jdsika @nicolasochem ready for review/merge.

[rvermootenct]

I have spent time looking through the code and the tests, as well as running and confirming that my reports are the same while on ghostnet and using dry run while on mainnet on the different reward network providers. From what I can see this PR is ready to go. Awesome work @vkresch

I will add a disclaimer that I am still new to TRD and may have missed important questions.

[rvermootenct]

I have spent time looking through the code and the tests, as well as running and confirming that my reports are the same while on ghostnet and using dry run while on mainnet on the different reward network providers. From what I can see this PR is ready to go. Awesome work @vkresch

I will add a disclaimer that I am still new to TRD and may have missed important questions.

[nicolasochem]

thank you @vkresch @rvermootenct