Make things more reusable, correct some errors along the SSH key path

Conflicts:
	library/user

if a module returns failed in the results, don't fail unless failed is n...

Improved lookup plugins

Pretty-print "msg" when task fails

Return original string for non-matched vars

Several modules (e.g., pip) return stdout and stderr together in a "msg" variable (and the module development docs seem to suggest that the standard practice is to return status in this variable).

This change ensures that it is printed out with correct formatting (most importantly, with newlines appearing as newlines instead of \n).

Use default port if ansible_ssh_port is not set for the delegated node

Also add testcase for it.

Requires that inject be passed to run

This allows using with_fileglob in play context, e.g.
- include: $item
  with_fileglob: tasks/*.yml
as well as prepares for other data to be passed.

Fix service module for varnish initscript in EPEL

It outputs 'dead but pid file exists'.

Make sure ownership is set correctly for user's new ssh keys

- Fixed some typos for the ansible config file in the man page

Add option create= to lineinfile module

fix up remove and fix fixme checking to see if pkg was removed

Add a group_by action plugin.

Fix typo

We use the lineinfile module to modify configuration files of a proprietary application. This application reads configuration options from files, but does not require those files to exist (if the default options are fine). However this application may modify the configuration file at will, so we cannot copy or template those files. And after a silent install the configuration may not exist (depending on the response file).

Whatever the case, during deployment we need to make sure some configuration options are set after the installation.

So the cleanest way to handle this situation is to allow the lineinfile module to create the file if it is missing (and this is the expected behavior). When I proposed this behavior, @sergevanginderachter needed the same functionality and was now working around it as well.

- added the ANSIBLE_CONFIG environment variable

Use return codes > 255 for Ansible-specific errors.

More useful error message for if not HAVE_SELINUX

I had made and pushed this change after you already pulled the request.

@dhozac indicated that it would probably be better to use return codes > 255 for anything related to Ansible itself. Which makes sens :)