Make `pip install -e` work

This allows `pip install -e` and `python setup.py develop` to work
without having to do the stuff in
http://docs.ansible.com/intro_installation.html#running-from-source so
it's a tad nicer for Python programmers who are accustomed to installing
packages as editable/in development mode.

Fixes GH-8355 (https://github.com/ansible/ansible/issues/8355)
fixes #8626 by reverting 0d8b81cd
Disallow args: to be specified as a string
Fix fonts in docs: Incosolata -> Inconsolata
Merge pull request #8367 from msabramo/make_pip_install_editable_work

Make `pip install -e` work
Merge pull request #8635 from RockinRoel/devel

Fix fonts in docs: Incosolata -> Inconsolata
Make env param a dict type instead of list

Also modifies param type checking code to remove whitespace from
around params before splitting them into k=v pairs.

Fixes #8199
Merge pull request #8627 from rghe/devel

fixes #8626 by reverting 0d8b81cd
Tense correction
Merge pull request #8641 from ianmiell/imiell_docs

Tense correction
Added winrm test for long-running command.
Fix bad commit from #8095 and fix bad splitting on :'s in the image

Fixes #8095
Fixes #8658
Make sure group_vars/all is loaded for ungrouped hosts

Fixes #6563
Add option to disable ControlPath to ssh options during rsync

Fixes #8473
Correct check for role library/ existence

Fixes #8633
Fix check mode issues with copy module

Fixes #8639
$powershellpath is called as ".$powershellpath"

$powershell path is set to "C:\powershell" at line 27. This is fine, but on line 82 $powershellpath is called as ".$powershellpath\$filename". Because the path at line 27 is absolute, a period preceding the $powershellpath is not required at 82. It actually causes an error:

Start-Process : This command cannot be executed due to the error: Unknown error (0x80041002).
At C:\users\Nathan Sosnovske\Documents\ps2to3.ps1:81 char:14

Start-Process <<<< -FilePath ".$powershellpath\$filename" -ArgumentList /quiet
CategoryInfo : InvalidOperation: (:) [Start-Process], InvalidOperationException
FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand
Removing the period on line 82 before $powershellpath fixes this error.
Set prompt encoding to a sane value when sys.stdout.encoding is None

Fixes #8644
In order to allow easier updates from upstream hardware vendors, we're going to be hosting network hardware
config modules on Galaxy as announced during the last release cycle.   (This excludes load balancers, which remain in core).

Please refer to https://eos.arista.com/introducing-arista-eos-roles-for-ansible/ and https://galaxy.ansible.com/list#/roles/1359
and where this content now lives.

Thanks to Peter Sprygada for the roles content!
When serializing inventory, pop from the start of the hosts list

Fixes #8646