Move encoding script to gist

Author: rjmholt

reference/docs-conceptual/components/vscode/vscode-encoding-configuration.md

@@ -243,41 +243,7 @@ In PowerShell 5+ you can find your default encoding with this:
 [psobject].Assembly.GetTypes() | ? { $_.Name -eq 'ClrFacade'} | % { $_.GetMethod('GetDefaultEncoding', [System.Reflection.BindingFlags]'nonpublic,static').Invoke($null, @()) }
 ```
 
-To find out what your PowerShell session will infer a script without a BOM to be encoded in, run:
-
-```powershell
-$badBytes = [byte[]]@(0xC3, 0x80)
-
-$utf8Str = [System.Text.Encoding]::UTF8.GetString($badBytes)
-
-$bytes = [System.Text.Encoding]::ASCII.GetBytes('Write-Output "') + $badBytes + [byte[]]@(0x22)
-
-$path = Join-Path ([System.IO.Path]::GetTempPath()) 'encodingtest.ps1'
-
-try
-{
-    [System.IO.File]::WriteAllBytes($path, $bytes)
-
-    switch (& $path)
-    {
-        $utf8Str
-        {
-            return 'UTF-8'
-            break
-        }
-
-        default
-        {
-            return 'Windows-1252'
-            break
-        }
-    }
-}
-finally
-{
-    Remove-Item $path
-}
-```
+To find out what your PowerShell session will infer a script without a BOM to be encoded in, run [this script](https://gist.github.com/rjmholt/3d8dd4849f718c914132ce3c5b278e0e).
 
 It's not strictly possible to force PowerShell to use an input encoding,
 and PowerShell 5.1 and below default to [Windows-1252] when there is no BOM.