Update steps for running WinAppDriver autonomously

[smilinrobin]

The steps in the current documentation leave ambiguity for the reader to figure out setup steps in a CI/CD kind of pipeline.
Adding details around batch files and Task Schedulers to run winappdriver autonomously would help automation/testing teams to setup Winappdriver in a complementary style to the CI/CD flow.
@timotiusmargo @hassanuz @licanhua @kat-y @DHowett - Kindly review and approve the PR as necessary .

[ghost]

All CLA requirements met.

[vagisha-nidhi195]

@smilinrobin Does the solution to pass the desktop session to a console session work? I have been able to connect with winappdriver on the console session but wehn clicking any element it results in the following error:

{"status":13,"value":{"error":"unknown error","message":"An unknown error occurred in the remote end while processing the command."}}

[licanhua]

what QRes.exe?

[smilinrobin]

@licanhua - We can setup Qres (http://qres.sourceforge.net/) or another remote vnc tool to change the resolution of the target machine to match the local machine. My solution is loosely derived from here : https://stackoverflow.com/questions/35862217/screen-resolution-changes-for-the-remote-machine-after-safely-closing-the-rdp-se .

Alternatively the user can skip setting up the destination resolution with QRes .

[smilinrobin]

Updated commit with the notes around Qres

[licanhua]

@kat-y and @DHowett Can you help to review and merge it? I think these handy scripts are very useful

[DHowett]

Thank you for this! I reworded it quite a bit.

[DHowett]

Suggested change

	5.WinAppDriver requires the Winappdriver server to be listening on the local host or IP address in order to perform the requisite UI interactions. While Appium generally takes care of this requirement on the local , for running on a server/remote machine, we need to perform a few extra steps as Winappdriver requires a GUI Output and the Winappdriver server running in an interactive shell.
	5. WinAppDriver requires the WinAppDriver server to be listening in order to perform the requisite UI interactions. While Appium generally takes care of this requirement on the local machine, running on a server/remote machine requires a few extra steps as WinAppDriver requires an interactive desktop session.

[smilinrobin]

Thanks @DHowett . 👍

[lovelyplanet2019]

I have setup a launch.bat file to call WinAppDriver.exe at test machine IP and port.
cmd start /K "C:/Program Files (x86)/Windows Application Driver/WinAppDriver.exe" 192.168.2.129 4723

Then Jenkins call the :
C:\Users\tester\Desktop\Jenkins\workspace\test_RF>CALL C:\prj-ewcom\launch.bat

At Jenkins console result: the WinAppDriver is exit automatically and cause the robot script failed.

C:\Users\tester\Desktop\Jenkins\workspace\test_RF>cmd start /K "C:/Program Files (x86)/Windows Application Driver/WinAppDriver.exe" 192.168.2.129 4723  
Windows Application Driver listening for requests at: http://192.168.2.129:4723/

Press ENTER to exit.

Exiting...

Anyone know how to configure Jenkins properly to run WinAppDriver ?