Make the setup a nicer experience

[lupinitylabs]

The setup process could be a lot nicer, and some of it even automated.

One issue has already been addressed in #38, but I think we can take this a lot further:

• In my case, running php artisan protector:token returned an http server url instead of https. If this is entered in the .env of the client, it will result in an Error retrieving dump from remote server: Status code 301. Found no file to import. error. Since the remote import feature will never work over a http, and we are obviously not following redirects to the https site anyway, we should check the server URL beforehand and give the user instructions on how to fix the issue. Additionally, the protector:token command should never give out a http URL in the first place, if that's not going to work.
• Consider automating setup over additional API routes, and the server admin could then just approve the keys that were sent in by the client. Once it is approved, an API route on the client could automatically apply the auth token and server URL in a secure manner.
• The documentation is hard to understand and at times misleading:
  
  These are the .env keys that need to be provided by the server admin. I don't quite understand what unless specified otherwise in your software is supposed to mean?