Module DOCUMENTATION: assemble, authorized_key, command, copy

Close zeromq context and socket.

  plus a small fix in rst.j2 template
  manpages generated & checked
  modules.html generated & checked

module_formatter fixes

Revert pull request #1091

Automatic quoting of variables in only_if breaks existing playbooks
where entire statements are put in a variable, and other cases. See
issue #1120 for details.

Various tweaking to get the module formatter to work for 'make docs' in the docs project.  Likely the templates for other module formatting types will have to change
by the time I'm done.

Revert only_if for variables and templating prompt, little practical use

Since the condition was not templated, it wasn't working.
Only variables in local scope were used, which made this not very practical

New module: manipulate INI-style settings

This fixes a few issues,
- ${foo}${bar} would be parsed as a variable named foo}${bar,
  which wouldn't be easily fixed without breaking ${foo.${bar}}
- allows escaping . in variable parts so e.g.
  ${hostvars.{test.example.com}.foo} works

This is slower than using re. 3 million templating calls take about
about twice as long to complete with this compared to the regexp,
from ~65 seconds to ~115 seconds on my laptop.

Fix only_if statements referencing non-string types

Remove assemble action plugin, fix daisychaining

Strip trailing white space from $FILE()/$PIPE()

This fixes e.g. only_if: ${task.changed} which would always
evaluate to true due to it having been replaced by a string for its
boolean value. Also adds a test case to ensure it doesn't get
missed again.

Don't use ssh-agent if password is specified.

The very first start of 'fireball mode', which uses ansible in SSH mode to deploy a ephemeral zeromq daemon (entirely optional) that is will die after
it is no longer used.  No key signing will be required.  At this point, development use only -- NOT complete.

split off examples from DOCUMENTATION into own array as per #1098

Ignore failure of stop command if start succeeds with state=restarted

In some cases (see issue #1067) with state=restarted, a failure to stop
the service (which wasn't running) would appear to the module to be a
failure to restart the service even though it successfully started the
service.  This changes the behavior of the service module to focus
on the return code of the start command.  If the rc of stop is not
0 and the rc of start does equal 0, it considers the service
successfully restarted.  It then ignores the rc, stdout, and stderr
from the unsuccessful stop command.

2 improvements to delegate_to

Getting negative host pattern matching to work with external inventory

Give nice error message if destination directory doesn't exist