* release:
  (MODULES-6246) Prep for release 2.1.3

(maint) - modulesync 384f4c1

(maint) modulesync cd884db Remove AppVeyor OpenSSL update on Ruby 2.4

Previously the travis.yaml file was unmanaged as it contained customisations not
compatible with modsync.  Now that the required options are available the sync
file can be updated accordingly.  This commit:
- Updates the sudo, dist and before_install commands to install Powershell
- Updates the NOTICE file to indicate the correct dates for the copyright
  holders

This commit applies modsync at commit a3ae5c94f7d

 - It's unnecessary to use PowerShell sub-expressions in the
   examples given. Remove superfluous syntax to prevent user confusion

  This appears to have been errantly introduced in
  f49c95f

(maint) Update sync.yaml for new modsync config options

The newest image for Windows 2008r2 is exhibiting different behavior
for loading .NET assemblies than we have seen in the past. The
System.Core assembly is not loaded into the PowerShell host process by
default any longer. This causes the init.ps1 script in the module to
to fail to start a Pipe Server to receive PowerShell scripts to be
executed. This change always attempts to load the System.Core
assembly prior to creating the pipe server object. Explicity loading the
assembly fixes the issue and the newest image becomes usable again. This
fix is also require to fix any moduels that depend on the PowerShell
exec provider working properly.

…x_assembly_loading_on_new_win_image

(IMAGES-795) 2008r2 template failing PowerShell module tests

This commit adds the testmode switcher gem and modifies the tests to use test
mode switcher.  This allows acceptance tests to run with or without a master.

…GES-795-fix_assembly_loading_on_new_win_image

Revert "(IMAGES-795) 2008r2 template failing PowerShell module tests"

The newest image for Windows 2008r2 is exhibiting different behavior
for loading .NET assemblies than we have seen in the past. The
System.Core assembly is not loaded into the PowerShell host process by
default any longer. This causes the init.ps1 script in the module to
to fail to start a Pipe Server to receive PowerShell scripts to be
executed. This change always attempts to load the System.Core
assembly prior to creating the pipe server object. Explicity loading the
assembly fixes the issue and the newest image becomes usable again. This
fix is also required to fix any modules that depend on the PowerShell
exec provider working properly.

…Fix-Pipe-server-on-2008

(MODULES-6927) Fix Pipe Server on Win 2008r2

…yntax-updates

(maint) Minor PowerShell syntax updates to README

…tcher

(MODULES-6750) Add testmode switcher

….1.4-release

(MAINT) Update changelog prior to 2.1.4 release

This commit updates the CHANGELOG.md and METADATA.json files to prep for
the 2.1.4 release of the module.

…-release-prep-2.1.4

(MODULES-6937) Release Prep 2.1.4