SecureString to plain text conversion using NetWorkCredential instead of marshalling

[santisq]

PR Summary

Context

Sent the PR to the wrong repo 😅. Also added a few more changes to Add-EnvPath (the logic could be simplified).

Changes

• .gitignore

Adding tools/Modules and output folder to .gitignore, otherwise the modules needed for CI/CD and the released module would get pushed to repository.

• .vscode/launch.json

Added launch file for easier debugging, i.e.: Ctrl+Shift+Enter opens a new pwsh with the module already loaded.

• .vscode/tasks.json

Added tasks file, easier building, i.e.: Ctrl+Shift+B runs build.ps1 and F1 -> Run Test Task runs build.ps1 -Task Test.

• SteamPS/Private/API/Get-SteamAPIKey.ps1

Using NetworkCredential to decrypt the secure string instead of marshalling. This method properly handles the unmanaged memory, makes it simpler and correctly frees the unmanaged memory.

Otherwise, if marshalling:

1. PtrToStringAuto should be PtrToStringBSTR instead to avoid encoding issues.
2. There should be a finally block in the function that calls [System.Runtime.InteropServices.Marshal]::ZeroFreeBSTR($BSTR) to free the unmanaged memory, otherwise the plain text password lives in unmanaged memory while the pwsh process is alive.

Both points above are correctly managed by NetworkCredential.

• SteamPS/Private/Server/Add-EnvPath.ps1

Using [System.IO.Path]::PathSeparator instead of ; to split the path in case you want to make this module compatible with Linux in the future (its separator is :). Trim() to remove any extra trailing or leading whitespace from each token and then filtering any token that could be purely white space, i.e.:

PS /> 'foo;; bar; baz ;;'.Split([System.IO.Path]::PathSeparator).Trim() -ne '' -join ';'
foo;bar;baz

• SteamPS/Private/Server/Get-SteamPath.ps1

Same change to split using [System.IO.Path]::PathSeparator.

Checklist

• Pull Request has a meaningful title.
• Summarised changes.
• Pull Request is ready to merge & is not WIP.
• Added tests / only testable interactively.
  • Make sure you add a new test if old tests do not effectively test the code changed.
• Added documentation / opened issue to track adding documentation at a later date.