shorten MN outpoint output from getvotes

[nmarley]

This would change the output of getvotes family of RPC commands from something like (example):

"64c9d5a7aed64fddf4f69390b4aec921938238a9efb4e81dab878d74234e1340": "CTxIn(COutPoint(a8b2a88c97682f213d3f71ffa2d0ae2e13220745c7fa7e2b93c2aff0824db4ff, 0), scriptSig=):1511282274:NO:FUNDING"

... to this:

"64c9d5a7aed64fddf4f69390b4aec921938238a9efb4e81dab878d74234e1340": "a8b2a88c97682f213d3f71ffa2d0ae2e13220745c7fa7e2b93c2aff0824db4ff-0:1511282274:NO:FUNDING"

This would make it easier to parse and remove superfluous chars. This has already been done for masternode status, so this change is following up on some remaining bits.

[UdjinM6]

utACK

[codablock]

Any reason we don't use json in such commands?

[nmarley]

The getvotes and getcurrentvotes commands do actually output JSON. The example that I posted is an excerpt, just showing one vote to show the differences this change would bring.

If you're asking why it's not broken out into separate fields and colon-delimited instead, my guess is that it's probably just simpler for serializing in the toString() method. But @UdjinM6 would probably know the history better than I would.

[UdjinM6]

I don't remember the exact reason for not using json. I guess it's just a legacy way of presenting things to make them somewhat readable in cli output by keeping them in one string/line per item form.