* Logging is now a sane module

* Raitonale - Logging was a haphazard piece of code at best. Moving forward, we plan on having a centralized Logging
  Repository - therefore, having just one customizable Logger would allow us to actually integrete this Logging system
  into place. Also, previous code did not respect it's boundaries (would read and write config files) and would do questionable
  things (split paths as raw strings based on '/' to create folders if they don't exist).
  All this has been rewritten to provide for one logging file which is used across 3 modules - adapter, VMManager and controller.

* API is split into two - create_logger() to create loggers and get_logger() to retreive a created logger
* no global loggers (logging.LOGGER) present
* all files have been modified to use the new get_logger() system
* modules which used subprocess used to access the file descriptor of the log file  as LOG_FD. this has been removed
* the config file has been changed - the field from which the logfile path has been renamed to LOG_FILE_PATH from LOG_FILENAME
* The primary module of each OVPL subsystem calls create_logger(), and the other modules use get_logger() to access these

TODO:
* integrete the web logging into this
* find some way to supply the file descriptor? not sure if this is required
* code reivew is yet to be done :)