nocows = 1 in ansible.cfg
	or old environment variable ANSIBLE_NOCOWS=1
add to ansible.cfg example

While here factor out password prompting in ansible.utils

allow references to names of variables in with_items without needing to surround them with Jinja2 '{{' delimeters

file.

Upgraded variable support met with upgraded conditional support, see examples/playbooks/upgraded_vars.yml
for details!

Fixes #2305.

Moved *jina* to *jinja2*

Jinja extensions adds features to the jinja2 templating engine. This
patch allows module loading for the templating engine vian an
ansible.cfg configuration key (jinja_extensions).
The default behaviour doesn't change (no module loading).
Requested modules can be added coma separated in ansible.cfg

Adds whitespace handling in jinja_extension config

Added whitespace handling in jinja_extension configuration directive, so
things stay safe if user adds spaces around comas in the directives
list.

Adds config example for jinja_extensions

Added config example with multiple extentions for jinja_extensions

Change the 0.X part to not imply something new was added in 0.X something if a user forgets to put in a specific version in the module docs.

Simply ensures existence or non-existence of a vhost.

Default to -H to set $HOME appropriately.

Typo

Hash variables are currently overriden if they are redefined. This
doesn't let the user refine hash entries or overriding selected keys,
which can, for some, be a desirable feature.
This patch let the user force hash merging by setting the
hash_behaviour value to "merge" (without the quotes) in ansible.cfg

However, by default, ansible behaves like it always did and if any value
besides "merge" is used ("replace" is suggested in the example ansible.cfg
file), it will also behave as always.