Add subcmds oasis network operators

[amela]

It would be nice to have a cli function that lists data regarding operators and optionally stores it in the CSV. Examples of cmds:

• oasis network operators < validators | sapphire | cipher | ... > -> it would list operators metadata and addr with their emails
• oasis network operators nodes -> it would list node versions with their operator's metadata, addr and emails

Alias: opers

[matevz]

Could this be part of the existing oasis network show validators and oasis network show nodes commands?

[amela]

@kostko @matevz
So, I tried to add these commands to oasis network show. The problem is that this command is becoming very bloated. I suggest the following:

Because the paratime section looks like this:
oasis paratimes show { <round> [ <tx-index> | <tx-hash> ] | parameters }

I think the oasis network show should be about consensus. So, I would there remove the following commands:
oasis network show { id | committees | entities | gas-costs | native-token | nodes | parameters | paratimes | validators }

I would move the removed commands to oasis operators section and put each command in its own file. Also add operators metadata where needed and extend the entities command to something like this:
oasis operators entities [id]
with the following flags:

--paratime sapphire //to list operators on sapphire or other selected paratime
--show status //to show all node statuses of selected operator

This command without the flags would output:

{
  "EntityName": "Staking Fund",
  "EntityAddr": "oasis1qr0jwz65c29l044a204e3cllvumdg8cmsgt2k3ql",
  "EntityID": "kfr2A6K6TlvhQm4nz88Hczzkd2Aq5PlkxSpnmUUBAFs=",
  "EntityNodes": [
    "lbxs4hlud9XNloIOdhJPaCahd7HtiY8QATCgGnFfCM0=",
    "KUjJArjDn1TtZOi6AgYki1fUTC2PrU0LJFJ4ppHt3NQ="
  ]
}

wdyt?