Allow variable expansion for vars that evaluate to false

Support systemd native services in the service module.

Most of it worked already, except for the enable parameter, because it
tried to use chkconfig which only sees SysV services. First look for
systemctl and use that if it exists.

Add a state parameter to the wait_for module.

fix up local_nvra and fix for a missing localinstall rpm file.

Add working CPU model fact for some ARM devices

Check for terminal capabilities if curses is available

Normally curses is part of the standard library, but this was not
always the case in the past.

The ANSIBLE_COLOR environment variable and the tty-check have
priority over the curses method (as they are both faster than
the curses test).

Works on Sheevaplug, probably works on Rasberry Pi as well

This takes started, stopped and restarted.

Started returns when connecting is possible.
Stopped when connecting is not possible.
Restarted first waits for connecting to be impossible and returns when it is
possible again.

Subversion

Allow change of ownership and checks for existing database

Change semantics of postgresql_user module

Add the wait_for module.

Issue #935: filter out __init__ module from the list of callbacks

This module waits until a specific port on a given host can be connected to.

scope error with utils.py branch_path

added force option to git - made both subversion and git default to force=true for backward compatibility with git's previous behavior

Fix git version when some head files are missing.

fix _gitinfo function to avoid ansible crashing in cases where the branch file is missing (e.g. after a gc)

Use a different method to query for current 
privileges at the table and database level. 
This method is more robust if newer privileges 
are added in future versions and also supports the 
ALL wildcard.

fail_on_user option can be used to ignore silently
if the user cannot be removed because of remaining
privilege dependencies to other objects in the 
database. By default it will fail, so that this new 
behavior won't surprise unsuspecting users.

The postgresql_user module has several drawbacks:
* No granularity for privileges
* PostgreSQL semantics force working on one
  database at time, at least for Tables. Which
  means that a single call can't remove all the 
  privileges for a user, and a user can't be
  removed until all the privileges are removed, 
  forcing a module failure with no way to 
  work around the issue.

Changes:
* Added the ability to specify granular privileges
  for database and tables within the database
* Report if user was removed, and add an option to 
  disable failing if user is not removed.