User module

This relies on useradd, usermod, and userdel utilities on the system.
The argument name is required; if state is not provided, present is
assumed.  Other options supported for creating or modifying an existing
account:  uid, gid, comment, home, shell, and password.  If managing the
password, it must already be encrypted.  When creating an account, you
can also provide the argument createhome to control whether the home
directory is created.  Arguments supported for deleting an account are:
force (remove account even if user is logged in) and remove (remove home
directory).

Allow groups to be passed to runner API to make parse_hosts optional, misc fixes as a result of refactoring in Runner.
Cleanup in Playbooks module is next.

misc cleanup in the runner module, splitting some things out into utils, breaking up functions into smaller functions.

Allow variable expressions to be stored as variables themselves, do some things to allow setup strings
to more easily contain spaces without being mangled, which is neccessary because of the above.

playbooks -- Ratchet up logging prior to gating things with verbosity controls and upgrading output format

Remove test from bottom of example that doesn't really make sense in the context of the example's use case.

refactoring of playbooks now warranted, which we'll do before we move on.   This variable assignment
system makes nearly all possible magic possible, for we can use these variables however we like,
even as module names!

(Using varReplace function originally from yum, thanks Seth)

Playbook test upgrades, made some notes about callbacks we need to add.  Still need to compare events
recieved vs expected so we can be notified if this test breaks, and also to add some more detailed
playbooks that use includes & async, etc.

Import cleanup, plus have /bin/ansible remind you if no hosts were matched by a pattern (for instance, assume
there was a typo in the pattern)

Remove "import *" from bin/ansible so we can use pyflakes, and remove unneeded imports in the process

Add the failtest module, primarily for easy development testing purposes.  RPMs/etc need not ship this.

Fixup the code that allows facter/ohai/other data to bubble up and be used in future action lines.  It's a niche
case compared to usage in templates but it should work and will be wanted later for conditional support.

Inside of runner, do not 'import *' from utils, so we can more easily tell where functions come from

Preserve changed data on file and template ops when the mode operations don't result in a change but the files
were still replaced.