This way an email will be sent to an admin if configured so they have a
chance to check what's going on.

Refers to #3

This usually happens when VS is building multiple projects at the same
time, hence running the prepare-script multiple times at once.

Megabytes have shown to be a bit clumsy in the configuration files, so
simply switch to the more useful Gigabytes unit.

Fixes #39

Refers to #36

Refers to #25

Refers to #24

Allow setting the log level explicitly from "Warn", "Info", "Debug" or
"Trace" in the configuration.

Default is "Info", fallback for invalid settings is "Debug".

Fixes #34

Fixes #32

- config validation
- reporting
- log file upload
- update-source folder structure
- permissions

Fixes #33

An exception would otherwise result in a silenced error as the output
would be discarded.

Fixes #30

They were accidentially removed in commit cf183560 believing they had been
correctly moved by Visual Studio when refactoring the code and just forgotten
in the directory hierarchy. Who could guess Windows is so ignorant when
resolving paths?

* tray app
* logging
* windows versions
* components + paths
* development

In addition, this cleans up the config / status files copying using the
new structure.

This is only useful if the package actually contains configuration files
for the given host. If that's the case use the switch, otherwise a
message about how to start it will be printed to the console.