explorer/parser: decode DaoVote calls + state

[Maxnflaxl]

Summary

Extends the Explorer rich-parser to fully decode the DaoVote governance contract. It was scaffolded but only recognised the method names, so vote/proposal arguments and tallies came through empty. Now:

Calls

• AddProposal — variant count + proposal text.
• Vote — voter, epoch, counter, and the per-proposal choices.
• MoveFunds — Funds Lock/Unlock. The user and amount are deliberately not decoded: they already show up in the generic Keys (AddSig) and Funds (FundsLock/FundsUnlock) columns of the invocation.

State

• Epoch stats — current + finalized epochs, with stake active / dividend-eligible.
• Proposals — per-proposal variant tallies (No/Yes for binary proposals) and total stake voted.
• User votes — per-voter ballots enumerated from the contract's UserVote logs (Env::LogReader): voter pubkey, stake (weight), and per-proposal choices.

Testing

Reparsed a mainnet explorer-node with the new parser: DaoVote now surfaces decoded calls, per-epoch / per-proposal tallies, and the per-voter User votes table.

[valdok]

Nice. One thing I'd change: DaoVote::Method::MoveFunds - no need to decode the "user" and "amount", because those will appear it general fields: the amount moved out of the contracts, and the method signature (user).
But overall it's ok

[Maxnflaxl]

Makes sense, thanks.