Bugfix: #8720 winrm.py: protocol.send_message() crashes with https

for local usage.

Generate warnings when users are shelling out to commands
rather than using modules

Can be turned off on a per-action line with the documented
warn=False flag. Can be turned off globally using
command_warnings = False in ansible config file.

Print out warnings using the standard playbook callbacks.

Created some additional tests in TestRunner.test_command
and also a demonstration playbook.

Update docs to include directories inside group_vars

Fixes #8670

Unarchive should work when parent directory is not writable

Fixes #8324
Improves #7667

rds_module: Fix AWS connection

Remove galaxy CLI tests that hit bitbucket as bitbucket is hanging tests - maybe replace with nice github examples later :)

Conflicts:
	lib/ansible/utils/__init__.py

Also fixes a bug whereby any changes to the route_tables were not
properly reflected by setting changed=True.

Fixes #8666

Avoid multiple blank lines with --syntax-check

Fixed typos

Corrected a simple syntax error in galaxy

Fixes #8681

  Only print a blank line between plays when also doing --list-hosts and/or
  --list-tasks, otherwise this output just a long list of blank lines, one for
  each play.

Ensure that the automated scm determination for github.com
repos still copes with .tar.gz archive files.

Handling .zip archives is left as an exercise for the interested reader

Fixes #8604

Fixed role name for
    - { role: 'lives/in/a/subdirectory' }
Should be 'lives/in/a/subdirectory', not just 'subdirectory'

`ansible-galaxy init --offline ...` can create a role without
talking to the galaxy api server
`ansible-galaxy install ...` only needs to talk to the galaxy api
server for galaxy roles, not tar files or scm archives
Fixed a bug in command line role installation

Older git archive commands create tar archives even with a tar.gz
extension. So change it to always create tar archives and have
the install_role method cope.

Removed ssh roles from the test case as they don't work unless
you can connect to bitbucket via ssh and have your key there.

Corrected a minor typo in error messages