Should not use SecureString if possible

[dkettman]

While looking into why 'Connect-DelineaPlatform' does not work on MacOS or Linux (read: Powershell Core), I came across on the official Microsoft docs this page (See the 'Note' in the Description section). This states that the SecureString functionality in Windows Powershell is not implemented in .NET Core (which includes Powershell Core). They suggest sticking to certificates or IWA if possible. They almost alluded to not bothering with encryption if a password is required because at some point, it will be plain text in memory. According to some SO posts I found, some suggested getting the password in plain text, using the password, then as soon as it is used null out the password. Some even suggested invoking the GC process if possible.

I know our goal isn't have this run in PowerShell core, but it will open up our supported platforms to MacOS and Linux if implemented. Figure we can table this until later, just wanted it tracked.