Perf regression in the `Microsoft.WinGet.CommandNotFound` module

[daxian-dbw]

There is report in PowerShell repo about Microsoft.WinGet.CommandNotFound not working with v7.5.2 (no feedback when a native command cannot be found).

When investigating the issue, I found there seems to be a perf regression in the WinGet feedback provider -- it cannot return results for most commands I tried within 300ms (the timeout we currently use): dsc, powertoys, yt-dlp, ffmpeg, 7zip.

Most of those I tried started to work after increasing the timeout to 600ms, but the 7zip one requires about 1000ms.

I believe the feedback provider design can be improved to allow more flexibility, but for now, I wonder if it's easier to make some perf improvements from the WinGet feedback provider side.