Use Winrm v2 and let winrm-fs do file uploads

[mwrock]

This PR accomplishes 3 things:

• Updates WinRM gem usage to 2.0 API
• Replaces file upload code with wintm-fs (same code used by test-kitchen, inspec and vagrant) with its 1.0 implementation its orders of mafnitude faster the the former implementation and no longer constrained to 8k chunks.
• Use one powershell based shell throughout an entire converge. This is simpler, faster and follows the same approach as test-kitchen.

[mwrock]

No longer WIP and tested using chef-provisioning-vsphere

[mwrock]

cc @tyler-ball @jkeiser

[tyler-ball]

Thanks @mwrock !

[hh]

We lost the ability to run powershell scripts after this PR, I commented on some possible fixes that will get us up and running again.

[hh]

@mwrock @tyler-ball we need to default to session.run_powershell_script and only use session.run_cmd if raw options are passed the :raw options
/cc @ajeba99

[hh]

https://github.com/chef/chef-provisioning/pull/488/files

[hh]

@mwrock @tyler-ball this is a must have! We need ExecutionPolicy Unrestricted in order to run powershell
/cc @ajeba99

[hh]

Setting shell to powershell here may get rid of the need for the :raw block above

[mwrock]

Hi @hh can you provide an example of what does not work? We made the breaking change in 2.0 to no longer support :raw and now all transport commands use a powershell shell.

[hh]

It's not so much around the :raw, it's more around the ExecutionPolicy

In https://github.com/chef/chef-provisioning/pull/543/files/45e94cc3dbd716c9dc6e380dbd94adf9aa15b28e#diff-72ecfcec074b5e5bdfc04d91922a92fcL44 we lost:

   machine.execute(action_handler, "powershell.exe -ExecutionPolicy Unrestricted -NoProfile \"& \"\"#{convergence_options[:install_script_path]}\"\"\"",

Which since chef-dk 0.18.26 results in:

    - write file C:\chef\install.ps1 on base-2012r2-2016-08-01
    [base-2012r2-2016-08-01] File C:\chef\install.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.
                             At line:1 char:3
                             + & "C:\chef\install.ps1"
                             +   ~~~~~~~~~~~~~~~~~~~~~
                                 + CategoryInfo          : SecurityError: (:) [], PSSecurityException
                                 + FullyQualifiedErrorId : UnauthorizedAccess

[hh]

#550 should fix it

[mwrock]

Ah I see. So the big difference with powershell in winrm v2's :powershell shell is that it takes you directly to a powershell session and does not go through a cmd.exe process. So downfall of calling powershell.exe from a powershell shell is you are creating another powershell process from a powershell process. There are 2 ways to work around this scenario:

1. Make sure your base images set a reasonable execution timeout
2. Call Set-ExecutionPolicy unrestricted as the first command. However this will persist

[ajeba99]

Added #551