- turn the logger (KIWILog) into a Singleton
  + eliminates the first argument for every constructor
  + enforces less sloppy testing code for log message checking
- add the logger to the design diagram as a singleton
- start over all design write up
- fixed $main::kiwi accesses according to new Singleton log class
- fixed KIWIQX command execution logging with new Singleton log class
- fixed object instantiation of KIWIXMLRepositoryData due to new
  Singleton based log object class
- Due to the new Singleton log class and the fix in KIWIQX to make use
  of it, all EXEC calls now lands in the logInfoMsg type of unit test
  framework. Thus I changed the ktLog.pm::loginfo function in the unit
  test functions to ignore EXEC loginfo messages and allow the unit
  tests to work again
- fixed use of sat solvable functions due to the Singleton
  log class changes. There were still some functions calls
  left which passes the $kiwi log object to the functions
- implement new consistency checks
  + do not allow the assignment of a group ID to known system groups
  + do not allow the profiles attribute on a <packages> section marked
    as bootstrap
  + do not allow the use of archives in a <packages> section marked
    as bootstrap
  + ensure the interface is unique within one <machine> definition
  + ensure the MAC is unique within one <machine> definition
- eliminate the getUsers_legacy method
- removed __checkNoProfsBootstrapPackages check. It's allowed
  to have profiles specified in the bootstrap packages. There
  are image descriptions which installs the entire system by
  bootstrap packages. Reason for this is if the packagemanager
  in the image is not compatible to the implementation in kiwi
  e.g SLE10. Other than that we officially support bootstrap
  only installation including all features of 'image' typed
  package sections.