UX: refine the logging strategy

[albertotirla]

as you probably noticed already, odilia reads text from the terminal, even if it's not in focus when that happens. Most times though, it's trying to read its own logs. Since odilia starts with log level set to debug and all of it is redirected to stdout, also because all speech is being done in odilia by interrupting the previous utterance, odilia will basically not even be able to read those logs, nor anything else on the screen. To fix that, roughly the following things have to happen:

• the log level option in the config file has to be used, currently it's only read
  if the log level is not present, the program will print a warning to stderr and assume info
• there will be a new option in the config file, log_file_path, which would be used to direct the logs to.
  Of course, the user must have permission to access that location, otherwise the program will just bale
  If said option doesn't exist, logs will be sent to stdout

Aside from keeping a fairly spam free terminal, this has the benefit of making it easier to submit bug reports, by setting log level to debug(now in the config file but in the future probably in a gui), and just attaching the file to an issue, nice and clean