Add new session parameter to win_psexec

[Xyon]

SUMMARY

Allows users to specify the Windows session they would like psexec to interact with, per the documentation for psexec around the -i flag.

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

win_psexec

ANSIBLE VERSION

ansible 2.7.0.dev0
  config file = None
  configured module search path = ['/home/xyon/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib64/python3.6/site-packages/ansible
  executable location = /usr/lib/python-exec/python3.6/ansible
  python version = 3.6.5 (default, Jul 24 2018, 10:14:42) [GCC 7.3.0]

ADDITIONAL INFORMATION

Prior to this change, you could only specify "interactive: yes", which would just pass the -i flag to psexec.exe. For many purposes this is sufficient, but on certain boxes this causes the command to attach to the services console session rather than the Desktop (on session 1) as might be expected.

If provided, the value of session is passed to the -i flag, causing psexec to attempt to attach there instead. This proves useful in environments such as Azure, on a Windows 10 machine, when attempting to spawn processes on the desktop.

If no value for session is provided, the behaviour is as before the change.

[ansibot]

cc @dagwieers @jborean93 @jhawkesworth @nitzmahone
click here for bot help

[dagwieers]

We prefer if the first entry of the description is the summary of what the parameter is for.
Subsequent entries can clarify how it is used. So I would do:

  session:
    description:
    - Specifies the session ID to use.
    - This parameter works in conjunction with parameter C(interactive).
    - It has no effect when C(interactive) is set to C(no).
    type: int
    version_added: '2.7'

[jborean93]

Have added the changelog fragment and edited the doc to match @dagwieers recommendations. Thanks @Xyon for the PR.

I've changed the code myself