Find-PSResource uses file name casing instead of nuspec or manifest

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.

Steps to reproduce

Find-PSResource is using the file name to pull the name of the package instead of the nuspec or module manifest resulting in incorrect casing.

Create a local repository and then copy down a package. In this example I used the PSResourceGet module from the manual download section.

Expected behavior

Find-PSResource -Repository test -Name Microsoft.PowerShell.PSResourceGet -Prerelease

Name                               Version Prerelease Repository Description
----                               ------- ---------- ---------- -----------
Microsoft.PowerShell.PSResourceGet 0.5.22  beta22     test       PowerShell module with commands for discovering, inst…

Actual behavior

Find-PSResource -Repository test -Name Microsoft.PowerShell.PSResourceGet -Prerelease

Name                               Version Prerelease Repository Description
----                               ------- ---------- ---------- -----------
microsoft.powershell.psresourceget 0.5.22  beta22     test       PowerShell module with commands for discovering, inst…

Error details

No response

Environment data

beta22

Visuals

No response

Start by reproducing Find-PSResource against a local repository using the PSResourceGet package, then compare the displayed name with the package's nuspec or module manifest. Done means Find-PSResource reports the manifest package name casing rather than the downloaded file name casing.