Should we move osmosisd export-derive-balances into a seperate tool outside of the binary?

[ValarDragon]

osmosisd export-derive-balances takes a state export of the chain, and derives the balances of every module. It breaks up the balances pretty nicely, merging where they lie from a variety of stores. (unclaimed airdrop, staked, unbonding, LP'd, LP'd-by-pool)

I imagine this tool becoming more powerful over time. Ideas include one version working against every old version of the binary, cosmwasm features per application, automatically fetching the state export, far more filtering as people want, easy conversion of components to percentage of total supply, renaming ibc denoms to native names, etc.

This tool may belong in a separate go module in the same repository, that can work against multiple osmosis versions. (But be installed as a secondary tool, similar to cosmovisor)

See the cosmovisor repo / readme for how this can be done: https://github.com/cosmos/cosmos-sdk/tree/master/cosmovisor

Alternatives are:

• It can live in a separate repository
• It can be in the osmosis repo as a command, just like it is now, but it needs own package for better code structuring more advanced work.