non-interactive and dry-run modes for verdi setup type commands

[DropD]

This concerns

• verdi setup
• verdi quicksetup
• verdi computer setup
• verdi computer configure
• verdi code setup
  and some others.

Motivation:

• easier to programmatically setup aiida / profiles / compute resources
• allows tesing without a lot of work to simulate a user inputting data
• allows copy pasting of setup command lines

Non-Interactive

• passing a flag (proposed: --non-interactive) guarantees that the command will not prompt for any information
• information is passed via arguments / options
• missing information leads to a helpful error message
• ideally the options also get accepted in interactive mode instead of interactive input

Dryrun

• passing a flag (proposed: --dry-run) guarantees no side effects on the file system / database
• as much code of the command as possible should still be run (helps with test coverage)
• in many cases it is helpful to output some data on what the side effects would have been

Ongoing work

There is a separate repository in which the next generation verdi commandline is being built: https://github.com/DropD/aiida-verdi.

There is a branch in which some of the commands are being backported into the current verdi commandline: https://github.com/DropD/aiida-core/tree/ricoh-verdi-backports.

[DropD]

PR #606 goes part of the way