Correctly calculate Client Deal Bytes for a given wallet address

[ianconsolata]

@lanzafame pointed out that the Client Power is currently using the Market Balance of an address to calculate power (

on-chain-voting/power-snapshot/utils/lotus_rpc.go

Line 147 in 9427514

resp, err := lotusRpcClient.Call(ctx, "Filecoin.StateMarketBalance", tipSetList)

), rather than the deal bytes. This means the client voting power is based on how much FIL they have spent on deals, not how many total bytes worth of deals they have submitted. This is incorrect. Instead, I believe we need to pull data from the StateMarketDeals endpoint (https://docs.filecoin.io/reference/json-rpc/state#statemarketdeals), and loop over all the deals for a wallet address to calculate the total deal bytes for that address.

This should only be the deal bytes of CURRENT deals. Expired deals should not be counted.

[ianconsolata]

One additional complexity -- as @rvagg pointed out earlier in a slack chat, with Direct Data Onboarding this approach is no longer comprehensive, because "there exists the category of non-verified, non-market ... pieces, which you don’t get to know who owns that piece, or even if that piece has an owner other than the SP, “sparkling data” is the term that’s been thrown around for this"

So it sounds like calculating client deal bytes this way would not include sparkling data.

[ianconsolata]

Addressed partially by #136 -- it still doesn't account for the issue with direct data onboarding, but does now correctly calculate deal bytes for deals made the standard way.