Init Indy Node should output Base58-encrypted verkey already

In the Steward Getting Started Guide

Shows that the verkey will come out looking something like this:

bfede8c4581f03d16eb053450d103477c6e840e5682adc67dc948a177ab8bc9b

Which to the best of my knowledge is a hexlified version of the verkey.  Later on, in the guide, to send the the client to add the Steward's node to the ledger, they must execute:

python3 -c "from plenum.common.test_network_setup import TestNetworkSetup; print(TestNetworkSetup.getNymFromVerkey(str.encode('bfede8c4581f03d16eb053450d103477c6e840e5682adc67dc948a177ab8bc9b')))"

If they send the hex version of their verkey, the transaction would be rejected.

I've been able to produce the Base 58 version of the verkey in Node.js with just a simple Base 58 library, decoding the hex verkey into a string and then encoding it with the library.

This way when the user gets to this step:

indy> ledger node target=<validator_verkey_in_Base58> node_ip=<validator_node_ip_address> node_port=<node_port> client_ip=<validator_client_ip_address> client_port=<client_port> alias=<validator_alias> services=VALIDATOR blskey=<validator_bls_key> blskey_pop=<validator_bls_key_pop>

They then use this base58 key they obtained above.

Can we make it so that the base58-encrypted key comes out when you run init_indy_node?