Agent allow for configurable log directory

[jmalobicky]

The Agent logs are currently stored within the application directory. As these logs roll over after 2MB, they can clutter this directory. It has been requested to allow for the log (current and archived) to go to a specific location on the host. This destination could be another folder inside the application directory (which is not removed if the Agent is removed), a different absolute directory on the same host environment or a network share (using a Windows mapped drive). This should be either supportable during the installer process (maybe as a selective checkbox that launches a screen after clicking Next?), allowing to select a location or configurable post-installation via the agent.properties. Not selecting a different location (or even showing that screen?) should use the default application installation directory for the logs.

Any upgrade to a current Agent installation, should only allow for a change to the agent.config and not prompt for a different destination.

[jmalobicky]

Possibly adjusting the shawl cmd to add --log-dir <PATH>. As a workaround, it would be possible to unregister the service and re-register with an updated shawl cmd string. Though this would need to be done each time there is an upgrade to the service.

The cluttered files may be somewhat not an issue as the --log-retain is default at 2. This value is pretty low, in my opinion, especially for a very busy interface. I will create another issue to have the --log-retain increased to something more significant.