Replace "wps_2" with "Windows PowerShell"

This updates New-AzAutomationDocument, there may be others.
We could probably just use "PowerShell" but I'm reasonably sure these Automation accounts are using Windows PowerShell 5.1, not PowerShell Core 6

Author: Jaykul

src/Automation/Automation/help/New-AzAutomationModule.md

@@ -22,11 +22,11 @@ New-AzAutomationModule [-Name] <String> [-ContentLinkUri] <Uri> [-ResourceGroupN
 The **New-AzAutomationModule** cmdlet imports a module into Azure Automation.
 This command accepts a compressed file that has a .zip file name extension.
 The file contains a folder that includes a file that is one of the following types: 
-- wps_2 module, which has a .psm1 or .dll file name extension 
-- wps_2 module manifest, which has a .psd1 file name extension
+- Windows PowerShell module, which has a .psm1 or .dll file name extension 
+- Windows PowerShell module manifest, which has a .psd1 file name extension
 The name of the .zip file, the name of the folder, and the name of the file in the folder must be the same.
 Specify the .zip file as a URL that the Automation service can access.
-If you import a wps_2 module into Automation by using this cmdlet or the Set-AzAutomationModule cmdlet, the operation is asynchronous.
+If you import a Windows PowerShell module into Automation by using this cmdlet or the Set-AzAutomationModule cmdlet, the operation is asynchronous.
 The command finishes whether the import succeeds or fails.
 To check whether it succeeded, run the following command:
 `PS C:\\\> $ModuleInstance = Get-AzAutomationModule -Name `ModuleName