Fixing a bug where no User environment variable for PSModulePath caused an error in Canonicolize-Path

Error shows when installing a PowerShell module into the Global level

Canonicolize-Path : Cannot bind argument to parameter 'Path' because it
is an empty string.
At C:\PsGet\PsGet.psm1:947 char:96
+ ... onicolize-Path $_ })   -contains (Canonicolize-Path $Destination)
+                    ~~
+ CategoryInfo          : InvalidData: (:) [Canonicolize-Path],
ParameterBindingValidationException
+ FullyQualifiedErrorId :
ParameterArgumentValidationErrorEmptyStringNotAllowed,Canonicolize-Path
Revert "Fixing a bug where no User environment variable for PSModulePath caused an error in Canonicolize-Path"

This reverts commit 3ca161f46f5999c36c9b61dd436c1a71715c4601.
Fixing a bug where no User environment variable for PSModulePath caused an error in Canonicolize-Path

Error shows when installing a PowerShell module into the Global level

Canonicolize-Path : Cannot bind argument to parameter 'Path' because it
is an empty string.
At C:\PsGet\PsGet.psm1:947 char:96
+ ... onicolize-Path $_ })   -contains (Canonicolize-Path $Destination)
+                    ~~
+ CategoryInfo          : InvalidData: (:) [Canonicolize-Path],
ParameterBindingValidationException
+ FullyQualifiedErrorId :
ParameterArgumentValidationErrorEmptyStringNotAllowed,Canonicolize-Path

The fix is to Trim additional semicolons from the newSessionValue which
break when we "-split ';'" on the PSModulePath by causing empty array
elements
Merge pull request #92 from paulmarsy/master

Fixing a bug where no User environment variable for PSModulePath caused an error in Canonicolize-Path