First-run wizard

[encryptio]

A bare hzc-client deploy will currently just error out with an authorization error if the user is brand new. We should instead make a first-run wizard for new users, something similar to what surge does. now also has a first-run wizard, but it only handles user creation, not project creation (the details of which come from package.json in their case.)

I think a first-run wizard walking you through account creation (optional, check ssh keys first) and project configuration (optional, check cloudconf first) would be super nice, and we can persist the data in .hz/cloudconf.toml to make further deploys trivial.

[encryptio]

As mentioned in #8, during project creation, we should give a usable random wordy subdomain name as the default during the subdomain prompt. Thus, they can just press enter if they don't want to think about it, or they can set a name they like immediately.

Some tricky edge cases to watch out for:

• The user might not have an SSH key at all (this is an untested code path in hzc-ssh, and may result in a misleading error message)
• The user may choose project names and domain names that already exist; we should validate these during the prompting, not just afterwards at deploy time.
• The command might not be running interactively. If STDIN is not a TTY, we should abort with an error instead of entering the wizard.

[encryptio]

Moving to devpreview; I think first impressions will be colored badly if we don't have this in our first preview release.

[mlucy]

The CLI part of this is mostly done. Once the web UI is written we should add these features:

• If no user has their public SSH key, we should print their public SSH key and link them to the page in the web UI where they can add it.
• If they can't deploy to any projects, we should link them to the page in the web UI where they can create a project.
  • Alternatively, we could consider creating one for them, but currently only the web UI knows how to do that. Any thoughts on this?