Update Profile with ModuleFast module path reports successful even if profile doesnt exist

This happened in vscode remoting to a windows machine but may be present elsewhere:

```
PS C:\Users\ESRT-Allied\Documents\PowerShell\Scripts> imf -verbose
VERBOSE: Updating PSModulePath to include C:\Users\ESRT-Allied\AppData\Local\powershell\Modules
VERBOSE: Using relative path $([environment]::GetFolderPath('LocalApplicationData'))\powershell\Modules instead of 'C:\Users\ESRT-Allied\AppData\Local\powershell\Modules' in profile
VERBOSE: Checked for relative destination
VERBOSE: PSModulePath $([environment]::GetFolderPath('LocalApplicationData'))\powershell\Modules already in profile, skipping...
VERBOSE: 🔎 No modules specified to install. Beginning SpecFile detection...
Install-ModuleFast: Could not find any required spec files in C:\Users\ESRT-Allied\Documents\PowerShell\Scripts. Verify the path is correct or provide Module Specifications either via -Path or -Specification
PS C:\Users\ESRT-Allied\Documents\PowerShell\Scripts> $profile
C:\Users\ESRT-Allied\Documents\PowerShell\Microsoft.PowerShell_profile.ps1
PS C:\Users\ESRT-Allied\Documents\PowerShell\Scripts> cat $profile
Get-Content: Cannot find path 'C:\Users\ESRT-Allied\Documents\PowerShell\Microsoft.PowerShell_profile.ps1' because it does not exist.
PS C:\Users\ESRT-Allied\Documents\PowerShell\Scripts> gc -raw $profile
Get-Content: Cannot find path 'C:\Users\ESRT-Allied\Documents\PowerShell\Microsoft.PowerShell_profile.ps1' because it does not exist.
PS C:\Users\ESRT-Allied\Documents\PowerShell\Scripts> gc -raw $profile.CurrentUserAllHosts
```

Start at the imf/Install-ModuleFast entry point and reproduce the verbose profile update with the reported missing $profile path. Check how the command determines whether the profile contains PSModulePath; done means its success report matches whether the profile actually exists and was updated.

Escrito por el modelo de indexación a partir del texto del issue.