Use base repo and account seed in cli

[asutula]

Gets the CLI in line with how the programatic API deals with repo locations:

• Removes repo flag from init and uses base-repo instead. It's optional and defaults to ~/.textile/repo.
• The daemon flag now uses base-repo instead of repo with the same default.
• The daemon flag takes an optional account-seed flag to specify which account to use. If left out, it defaults to the first sub directory inside base-repo
• Same thing for migrate flag

[asutula]

Added a little optimization where, if you there are multiple account initialized in the base repo location and you don't specify an account seed, it fails and tells you to provide an account seed. So, the only time you can omit account seed is when there is only one account initialized.

[asutula]

Ok @sanderpick re: lock file... what do you think the lock file will be used for?

[asutula]

To update the original PR description with the current state of affairs:

• The daemon flag takes an optional account-address flag to specify which account to use. If left out, it defaults to the single sub directory inside base-repo, or errors out if there is more than one
• Same thing for migrate flag

[sanderpick]

A file (not really a lock file)... would be handy under the base repo to determine which repo is "active" / logged in to. This way you wouldn't have to always specify account address when starting the node, which requires that state to be kept somewhere (in my 1pass or in the containing app, for example). You could just write the account address into this file.

[asutula]

Ok I understand the idea. Would that state be updated any time you do specify an account address to daemon and/or migrate?

It's not really blocking this current work, so maybe I'll add this now, but maybe save it for another PR?

[sanderpick]

yeah, specifying the address would mean "change account". agreed, not blocking this one...