Set back the tls support and solve Issues #206

[tunisiano187]

---

This change is 

[tunisiano187]

Solve correctly the issue #206

[matthewprenger]

Edit: Installing .NET 4.8, even though PowerShell doesn't use it, allows for the Tls13 value to be resolved.

It looks like this breaks compatibility with at least Server 2016 since Tls13 isn't present in the SecurityProtocolType enum. Will have to look into how to support 1.3 in a backwards compatible manor.

PS C:\> [System.Environment]::OSVersion.Version

Major  Minor  Build  Revision
-----  -----  -----  --------
10     0      14393  0


PS C:\> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.14393.3866
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.3866
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1


PS C:\> [System.Net.ServicePointManager]::SecurityProtocol = 'Tls,Tls11,Tls12,Tls13'
Exception setting "SecurityProtocol": "Cannot convert value "Tls,Tls11,Tls12,Tls13" to type "System.Net.SecurityProtocolType". Error: "Unable to match the identifier name Tls,Tls11,Tls12,Tls13 to a valid
enumerator name. Specify one of the following enumerator names and try again:
SystemDefault, Ssl3, Tls, Tls11, Tls12""
At line:1 char:1
+ [System.Net.ServicePointManager]::SecurityProtocol = 'Tls,Tls11,Tls12 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], SetValueInvocationException
    + FullyQualifiedErrorId : ExceptionWhenSetting

PS C:\> [System.Net.ServicePointManager]::SecurityProtocol = 'Tls,Tls11,Tls12'
PS C:\> [System.Net.ServicePointManager]::SecurityProtocol
Tls, Tls11, Tls12