Enable executing Willie from outside the source directory

[embolalia]

This is something that seems like a minor issue, since we're so used to running willie from its source directory. Nonetheless, as a video @elad661 showed me points out, this isn't something that should be the case for a full-fledged FOSS project. I don't imagine this will be terribly hard to do, but there are some questions about how it should be done.

The primary problem at the moment is that it assumes that modules will be in the modules/ subdirectory of the current directory. Having modules available in the modules/ subdirectory of the source directory makes sense. I wonder, though, if we should enable a default per-user location for additional modules, say ~/.willie/modules, in case someone decides to install Willie system-wide for whatever reason.

[elad661]

Still needs fixing:

• Make logging path configurable, default to ~/.willie/logs/
• Move pid files to /run/willie or /var/run/willie
• Make sure we don't write anything to willie's directory - all files we write during runtime should be in dotdir!
• Make a distutils based installer

[elad661]

config.py line 245 still has os.getcwd(), it seems to be looking for modules there.

Should use os.path.dirname(os.path.abspath(__file__)) instead.

[embolalia]

Actually, looking at it, I think it needs to be removed entirely. It uses enumerate_modules to find the filenames. The cwd stuff is added to the path, which I don't think we need or want. Though, it also has trouble configuring modules when run on its own, due to imports in modulues. Should we add another command line option to willie.py to handle running the config script on its own? Split out the wizard into another file for the root directory?

[embolalia]

Config util now works as arguments to the main script, so this issue can be closed.