Make interactive installer for STACI

[RandomSort]

Do you want Jira? [Y/n] So on and so forth. Could be written to properties file or just installed. Install could be interactive if no staci.properties exist. Make the easy choices easy to make.

[buep]

And maybe when using interactive, write the staci.properties for the user as reference for later.

[martinmosegaard]

Started work on interactive mode, but there is some design work to do here: The current approach tries to share an installStaci function between interactive mode and the other mode, which I call property mode -- reading property files.

But throughout all functions, the get_Property functions dominate. They all fail if property files do not exist. One option is to refactor installStaci and child functions to take input arguments instead of using get_Property. That is a lot of work. Another option is to refactor get*Property to take a "default value" argument, which can be used if a property file does not exist. This has a couple of drawbacks or at least side effects to consider:

• If a file exists, but user runs in interactive mode, user will not be asked about which machines to create.
• The default values will be mirrored between the *.properties.template files and the functions.

[martinmosegaard]

Some options can get a nice default value based on the environment. For example the provider_type should default to virtualbox on Mac and none on Linux.

And the current default for browser_cmd is not likely to work on a Mac.

[martinmosegaard]

Needs grooming, break down into smaller tasks