Typo in docs
Fix Jinja2 filter plugins initialization

_get_filter_plugins() checks FILTER_PLUGINS against None hence
the latter should be initialized to None.
Playbook + with_items was an undocumented feature that was causing problems because it would
evaluate and replace '$item' with ''.  Really it doesn't make sense to include multiple playbooks
via a loop variable, as you can do this with task + with_items already (and it's a simpler code
path).  Given this is undocumented, this removes that feature, and we'll consider next how to
also add 'with_items' support directly to roles.
Add base64 encode and decode filters to templates
Fix some items related to playbook includes and indentation.
Since we removed the (undocumented) playbook include + with_items code, fix the tests to
compensate.
Allow jinja2 evals that produce lists to be used in with_items.  Ideally want something a bit less heavy
than the eval here.
Use safe_eval vs eval.
Enable usage of when_set within new eval system.
Style fixes so "make pep8" is clean.
Allow $foo and {{ bar }} to be used on the same line in playbooks.
Use Jinja2 strict undefined in string templating to allow the default filter to be used.
Add code to flag legacy templating like $foo.{bar} as deprecated in favor of Jinja2 {{ foo.bar }} so we
can remove the legacy system at a later date.
Allows Jinja2 that starts a YAML line to not cause a syntax error.

Technically this isn't quite valid YAML when this happens, so we make it valid.  This means that if a future commander
API allows save/load it should make sure it does similar processing.
Minor formatting
allow references to names of variables in with_items without needing to surround them with Jinja2 '{{' delimeters
Some continued work on new-style templates and associated test code changes.  Legacy template functions
are marked with "legacy_" for possible future removal.
Changes for 'make pep8'
Make lookup plugins accessible in templates
Decided to not deprecate legacy template syntax for now.  Backwards compat is important, though the docs will suggest the new way.