separation of account adding process from creation of Beet wallet

Ideally the user would **first** create a Beet wallet, and **then** go about adding accounts:

1. For creating a Beet wallet, I would suggest letting the user enter the wallet name and password on the same screen. Perhaps encourage a backup after the wallet is created. Then you can prompt user to add their first account.

2. For adding accounts, it would be helpful to have an "Add Account" title/header at the top. Also, I think you can let the user enter the blockchain and other info on the same screen.

By the way, is it really necessary (or even useful) to enter account name? Is it not the case that only the private keys are necessary (aside from bitshares cloud wallet) and the account name could then be be looked up?

No files or tests are named. Start by reviewing the wallet-creation and account-adding screens, then define the separate flows and required fields described in the issue; done means users can create a wallet before adding accounts and can add account details in the revised flow.

Written by the indexing model from the issue text.