🐛 Some classic paths not able to be processed correctly (#72)

Some classic paths were not casting to the correct versions, such as PowerShellGet, during a -Update check. Those should be working correctly now.

Fixes #69

Author: JustinGrote

ModuleFast.psm1

@@ -1776,7 +1776,7 @@ function Find-LocalModule {
       $manifestPath = Join-Path $moduleFolder $manifestName
 
       if (Test-Path $ModuleFolder) {
-        $candidatePaths.Add([Tuple]::Create($moduleVersion, $manifestPath))
+        $candidatePaths.Add([Tuple]::Create([version]$moduleVersion, $manifestPath))
       }
     } else {
       #Check for versioned module folders next and sort by the folder versions to process them in descending order.
@@ -1807,7 +1807,7 @@ function Find-LocalModule {
           }
         }
 
-        $candidatePaths.Add([Tuple]::Create($version, $PSItem))
+        $candidatePaths.Add([Tuple]::Create([Version]$version, $PSItem))
       }
     }
 
@@ -1820,7 +1820,7 @@ function Find-LocalModule {
         #NOTE: This does result in Import-PowerShellData getting called twice which isn't ideal for performance, but classic modules should be fairly rare and not worth optimizing.
         [version]$classicVersion = (Import-ModuleManifest $classicManifestPath).ModuleVersion
         Write-Debug "${ModuleSpec}: Found classic module $classicVersion at $moduleBaseDir"
-        $candidatePaths.Add([Tuple]::Create($classicVersion, $moduleBaseDir))
+        $candidatePaths.Add([Tuple[Version, String]]::new($classicVersion, $moduleBaseDir))
       }
     }