Env Simplification, URL-decoding symbols in Procedures

[masonville17]

Hey- so this is pretty short but let me know if you'd prefer me to break it up at all. It's just a few things that have changed on our end this week -

1- making sure the GUI and env stuff stays decoupled from init
2- simplifying init with existing reusable user-input methods
3- url decoding task and procedure names (we found some ampersands were url-encoded recently)
4- allowing empty passwords option (for users with vaulted / encrypted org passwords, these can show up as blank)

notes on init and envs -
I've set up the environment variables to null-coalesce to the select-objectfromlist method that we already have there. This is just to tidy things up a bit as things grow.

the env vars now just stay as bool
the number -> read-host -> bool assignment in switch works but better to keep things just as bool if thats how they are gonna be used. Plus it makes it so we dont have to make another GUI build if a one changes place with a two in the questionairre

updated gui exe is included which templates envs with these boolean values directly, where applicable

[masonville17]

I also left this formatting for the imports on supporting tasks or post-tasks

if (-not (Get-Command -Name Get-SimilaritySafe -ErrorAction SilentlyContinue)) { . "$($(get-childitem -path "." -Recurse -file "normalize-string.ps1" | Select-Object -first 1).fullname)"}

this just makes sure that it can import dependent methods even if post-job is invoked after the fact (otherwise using relative $PSSCriptRoot will fail to resolve dependency path)