Fails when package name contains a special characters

[taoyouh]

Steps to reproduce:

1. Create a new project using the WinUI 3 two-project template. There will be a MSIX packaging project called xxx (Packaged) which contains a space and a pair of parentheses.
2. Use StoreBroker to create a submission containing that msixupload (using New-SubmissionPackage).
3. The command fails saying:

Read-AppPackageBundleMetadata : Cannot validate argument on parameter 'AppPackagePath'. Cannot bind argument to parameter 'Path' because it is an empty string.
At C:\Users\appveyor\Documents\WindowsPowerShell\Modules\StoreBroker\StoreBroker\StoreBroker\PackageTool.ps1:2204 char:20

Error detail:
See the following code. It tries to find the msix package declared in the manifest.

StoreBroker/StoreBroker/PackageTool.ps1

Lines 2312 to 2314 in abd0007

	$searchPath = Join-Path -Path $expandedContainerPath -ChildPath (Split-Path -Path $application.FileName -Parent)
	$searchFilename = Split-Path -Path $application.FileName -Leaf
	$appPackageFilePath = (Get-ChildItem -Recurse -Path $searchPath -Include $searchFilename).FullName

In the manifest of my project, the package name is UniversalFtpServer (Package)_1.4.1.0_x86.msix, but the actual file is UniversalFtpServer%20%28Package%29_1.4.1.0_x86.msix. The idfference makes StoreBroker unable to find the correct msix package and fail.

[riverar]

Just making a note here that we helped another customer with this. If you're using the Packaging Project in Visual Studio, ensure its name doesn't contain (Package), similar to what was mentioned above.